public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/41988] [4.5 Regression] FAIL: g++.dg/debug/*.C -gdwarf-2 -g1 (internal compiler error) Date: Sun, 22 Nov 2009 22:32:00 -0000 [thread overview] Message-ID: <20091122223242.12724.qmail@sourceware.org> (raw) In-Reply-To: <bug-41988-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from howarth at nitro dot med dot uc dot edu 2009-11-22 22:32 ------- The last build I have from 20091002 without the problem is most likely r152421 which would bracket us between that and r152434 with the first recorded failure. This would leave the LTO merge itself and URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152429 Log: * mangle.c (write_unnamed_type_name): Implement. (local_class_index): Split out from... (discriminator_for_local_entity): ...here. (nested_anon_class_index): New. * cp-tree.h (TYPE_FUNCTION_SCOPE_P): New. as candidates. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41988
next prev parent reply other threads:[~2009-11-22 22:32 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-08 14:25 [Bug debug/41988] New: " dominiq at lps dot ens dot fr 2009-11-08 15:25 ` [Bug debug/41988] " rguenth at gcc dot gnu dot org 2009-11-08 17:03 ` pinskia at gcc dot gnu dot org 2009-11-13 15:11 ` ubizjak at gmail dot com 2009-11-13 16:45 ` hjl dot tools at gmail dot com 2009-11-13 16:57 ` pinskia at gcc dot gnu dot org 2009-11-13 16:58 ` pinskia at gcc dot gnu dot org 2009-11-13 20:23 ` hjl dot tools at gmail dot com 2009-11-13 20:32 ` pinskia at gcc dot gnu dot org 2009-11-13 20:35 ` pinskia at gcc dot gnu dot org 2009-11-13 20:38 ` hjl dot tools at gmail dot com 2009-11-13 20:44 ` dominiq at lps dot ens dot fr 2009-11-22 22:11 ` howarth at nitro dot med dot uc dot edu 2009-11-22 22:27 ` howarth at nitro dot med dot uc dot edu 2009-11-22 22:32 ` howarth at nitro dot med dot uc dot edu [this message] 2009-11-23 0:16 ` howarth at nitro dot med dot uc dot edu 2009-11-23 0:31 ` howarth at nitro dot med dot uc dot edu 2009-11-23 1:01 ` howarth at nitro dot med dot uc dot edu 2009-11-25 21:12 ` pinskia at gcc dot gnu dot org 2009-11-27 11:13 ` rguenth at gcc dot gnu dot org 2009-12-01 17:28 ` dominiq at lps dot ens dot fr 2009-12-01 22:07 ` howarth at nitro dot med dot uc dot edu 2009-12-01 23:21 ` dominiq at lps dot ens dot fr 2009-12-02 2:19 ` howarth at nitro dot med dot uc dot edu 2009-12-02 2:24 ` howarth at nitro dot med dot uc dot edu 2009-12-02 3:45 ` howarth at nitro dot med dot uc dot edu 2009-12-02 6:16 ` dominiq at lps dot ens dot fr 2009-12-02 14:45 ` dodji at gcc dot gnu dot org 2009-12-02 14:52 ` dominiq at lps dot ens dot fr 2009-12-03 5:03 ` 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=20091122223242.12724.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: 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).