public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/49084] [4.7 regression] bootstrap failure with Ada enabled Date: Sun, 13 Nov 2011 10:30:00 -0000 [thread overview] Message-ID: <bug-49084-4-GU6obVsA8l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49084-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49084 Kai Tietz <ktietz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ktietz at gcc dot gnu.org --- Comment #7 from Kai Tietz <ktietz at gcc dot gnu.org> 2011-11-13 06:00:35 UTC --- Hmm, this is due usage of "%lld" in printf-formatter. Does following patch fix your issue? Index: implicit-zee.c =================================================================== --- implicit-zee.c (revision 180840) +++ implicit-zee.c (working copy) @@ -944,10 +944,12 @@ VEC_free (rtx, heap, zeinsn_del_list); if (dump_file && num_ze_opportunities > 0) - fprintf (dump_file, "\n %s : num_zee_opportunities = %lld " - "num_realized = %lld \n", + fprintf (dump_file, "\n %s : num_zee_opportunities = " + HOST_WIDEST_INT_PRINT_DEC + " num_realized = "HOST_WIDEST_INT_PRINT_DEC "\n", current_function_name (), - num_ze_opportunities, num_realized); + (HOST_WIDEST_INT) num_ze_opportunities, + (HOST_WIDEST_INT) num_realized); df_finish_pass (false); return 0;
next prev parent reply other threads:[~2011-11-13 6:00 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-20 16:44 [Bug ada/49084] New: Bootstrap failure with bug box of Program_Error EXCEPTION_ACCESS _VIOLATION / Error detected at system.ads:175:5 anhvofrcaus at gmail dot com 2011-05-22 9:19 ` [Bug ada/49084] [4.7 regression] bootstrap failure with Ada enabled ebotcazou at gcc dot gnu.org 2011-05-23 19:09 ` anhvofrcaus at gmail dot com 2011-08-02 14:13 ` rguenth at gcc dot gnu.org 2011-08-02 15:41 ` anhvofrcaus at gmail dot com 2011-08-02 20:28 ` anhvofrcaus at gmail dot com 2011-08-04 16:02 ` anhvofrcaus at gmail dot com 2011-10-10 11:51 ` rguenth at gcc dot gnu.org 2011-11-13 10:30 ` ktietz at gcc dot gnu.org [this message] 2011-11-15 4:05 ` anhvofrcaus at gmail dot com 2011-11-22 22:00 ` cestrauss at gmail dot com 2011-11-24 3:29 ` cestrauss at gmail dot com 2011-11-27 21:30 ` cestrauss at gmail dot com 2011-11-27 22:40 ` ebotcazou at gcc dot gnu.org 2011-11-28 1:23 ` cestrauss at gmail dot com 2011-12-04 22:00 ` ebotcazou at gcc dot gnu.org 2011-12-08 1:24 ` cestrauss at gmail dot com 2011-12-11 0:24 ` cestrauss at gmail dot com 2011-12-11 8:33 ` ebotcazou at gcc dot gnu.org 2011-12-13 9:21 ` ktietz at gcc dot gnu.org 2011-12-13 10:08 ` ebotcazou at gcc dot gnu.org 2011-12-13 10:28 ` ebotcazou at gcc dot gnu.org 2011-12-13 11:25 ` ebotcazou at gcc dot gnu.org 2011-12-13 11:30 ` ebotcazou at gcc dot gnu.org 2011-12-14 1:04 ` cestrauss at gmail dot com 2011-12-16 16:26 ` anhvofrcaus at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-49084-4-GU6obVsA8l@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).