public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/41397] [4.5 regression] RTL checking failure compiling libiberty
Date: Fri, 18 Sep 2009 10:03:00 -0000	[thread overview]
Message-ID: <20090918100315.31543.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41397-226@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jakub at gcc dot gnu dot org  2009-09-18 10:03 -------
See the dwarf2out.c part of
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg01017.html
which fixes this.
If approved separately, I could commit just that part.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |jakub at gcc dot gnu dot org
                   |dot org                     |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-09-18 10:03:14
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41397


  parent reply	other threads:[~2009-09-18 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18  9:26 [Bug bootstrap/41397] New: " ebotcazou at gcc dot gnu dot org
2009-09-18  9:56 ` [Bug bootstrap/41397] " ebotcazou at gcc dot gnu dot org
2009-09-18 10:03 ` jakub at gcc dot gnu dot org [this message]
2009-09-18 10:06 ` ebotcazou at gcc dot gnu dot org
2009-09-18 23:17 ` jakub at gcc dot gnu dot org
2009-09-18 23:26 ` jakub at gcc dot gnu dot org
2009-09-20 20:59 ` pinskia at gcc dot gnu dot org

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=20090918100315.31543.qmail@sourceware.org \
    --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).