public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/26881] [4.1 Regression] internal compiler error in dwarf2out_finish
Date: Tue, 17 Oct 2006 11:31:00 -0000 [thread overview]
Message-ID: <20061017113046.12246.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26881-5699@http.gcc.gnu.org/bugzilla/>
------- Comment #21 from rguenth at gcc dot gnu dot org 2006-10-17 11:30 -------
Subject: Bug 26881
Author: rguenth
Date: Tue Oct 17 11:30:28 2006
New Revision: 117823
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=117823
Log:
2006-10-17 Richard Guenther <rguenther@suse.de>
Backport from mainline:
2006-05-11 Jan Hubicka <jh@suse.cz>
PR debug/26881
* Makefile.in (gt-cgraphunit.h): Add.
* cgraphunit.c: Include gt-cgraphunit.h.
(local_static_output): New static vector.
(cgraph_varpool_assemble_decl): Defer outputting debug info
for local statics to...
(cgraph_varpool_debug_local_statics): ... here.
(cgraph_optimize): Use it.
2006-05-12 Jakub Jelinek <jakub@redhat.com>
PR debug/26881
* gcc.dg/debug/pr26881.c: New test.
Added:
branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/debug/pr26881.c
Modified:
branches/gcc-4_1-branch/gcc/ChangeLog
branches/gcc-4_1-branch/gcc/Makefile.in
branches/gcc-4_1-branch/gcc/cgraphunit.c
branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26881
next prev parent reply other threads:[~2006-10-17 11:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 1:50 [Bug debug/26881] New: " dbaron at dbaron dot org
2006-03-27 1:52 ` [Bug debug/26881] " dbaron at dbaron dot org
2006-03-27 1:56 ` [Bug debug/26881] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-03-27 1:57 ` pinskia at gcc dot gnu dot org
2006-03-27 2:08 ` pinskia at gcc dot gnu dot org
2006-03-27 8:17 ` rguenth at gcc dot gnu dot org
2006-04-06 16:21 ` pinskia at gcc dot gnu dot org
2006-04-16 13:07 ` couriousous at mandriva dot org
2006-04-16 19:10 ` mmitchel at gcc dot gnu dot org
2006-04-19 13:01 ` jakub at gcc dot gnu dot org
2006-04-30 14:31 ` hubicka at gcc dot gnu dot org
2006-05-05 12:26 ` jakub at gcc dot gnu dot org
2006-05-10 20:08 ` flash at pobox dot com
2006-05-25 2:47 ` mmitchel at gcc dot gnu dot org
2006-05-29 8:54 ` martin at mpa-garching dot mpg dot de
2006-07-14 12:26 ` falk at debian dot org
2006-08-07 8:02 ` hubicka at gcc dot gnu dot org
2006-08-07 9:48 ` stephan at s11n dot net
2006-08-18 4:20 ` pinskia at gcc dot gnu dot org
2006-08-20 9:14 ` rguenth at gcc dot gnu dot org
2006-08-20 12:47 ` hubicka at ucw dot cz
2006-08-24 13:31 ` hubicka at gcc dot gnu dot org
2006-10-14 16:49 ` [Bug debug/26881] [4.1 " tbm at cyrius dot com
2006-10-17 11:31 ` rguenth at gcc dot gnu dot org
2006-10-17 11:31 ` rguenth at gcc dot gnu dot org [this message]
2006-10-17 11:33 ` rguenth at gcc dot gnu dot org
2006-10-30 7:32 ` sur at compart dot net
2006-10-30 17:03 ` pinskia at gcc dot gnu dot org
2006-10-30 18:23 ` sur at compart dot net
2007-02-02 11:18 ` rguenth at gcc dot gnu dot org
2007-02-13 0:38 ` pinskia at gcc dot gnu dot org
2007-03-07 10:09 ` rguenth 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=20061017113046.12246.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).