public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cestrauss at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/49084] [4.7 regression] bootstrap failure with Ada enabled
Date: Tue, 22 Nov 2011 22:00:00 -0000	[thread overview]
Message-ID: <bug-49084-4-ygp5b3YcEN@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

--- Comment #9 from Cesar Strauss <cestrauss at gmail dot com> 2011-11-22 21:49:37 UTC ---
(In reply to comment #7)
> Hmm, this is due usage of "%lld" in printf-formatter.  Does following patch 
> fix your issue?

I did encounter the build failure reported in comment #6 (unknown conversion
type character 'l' in format) on i386-pc-mingw32, and the patch given in
comment #7 did fix this failure for me.

A similar solution is also needed in gcc/ira-color.c
(print_hard_regs_subforest), where %lld is also used.

This allowed the build to continue to the point where I could reproduce the
failure described in comment #8.


  parent reply	other threads:[~2011-11-22 21:50 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
2011-11-15  4:05 ` anhvofrcaus at gmail dot com
2011-11-22 22:00 ` cestrauss at gmail dot com [this message]
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-ygp5b3YcEN@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: link
Be 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).