public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/29614] [4.2/4.3 Regression] DWARF information for function static variable is missing after unrelated code addition
Date: Thu, 21 Dec 2006 23:20:00 -0000 [thread overview]
Message-ID: <20061221232044.6915.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29614-9863@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from sje at cup dot hp dot com 2006-12-21 23:20 -------
This bug only occurs when NOT in -funit-at-a-time mode. Is there a plan to
switch all front-ends to unit-at-a-time compilation (which will fix this bug)
or is it still worth coming up with a fix for NON unit-at-a-time usage? The
problem seems to be when moving declarations from the varpool_nodes_queue to
the varpool_assembled_nodes_queue in varpool_assemble_pending_decls
(varpool.c). This routine gets called multiple times with a decl and we wind
up putting a declaration on the varpool_assembled_nodes_queue multiple times,
messing up the next_needed links in this linked list.
--
sje at cup dot hp dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sje at cup dot hp dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29614
next prev parent reply other threads:[~2006-12-21 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 12:43 [Bug debug/29614] New: " fnf at specifixinc dot com
2006-10-28 18:49 ` [Bug debug/29614] [4.2/4.3 Regression] " pinskia at gcc dot gnu dot org
2006-12-21 23:20 ` sje at cup dot hp dot com [this message]
2006-12-22 0:54 ` hubicka at ucw dot cz
2007-02-19 20:36 ` mmitchel at gcc dot gnu dot org
2007-02-20 21:40 ` patchapp at dberlin dot org
2007-02-24 0:11 ` sje at gcc dot gnu dot org
2007-03-05 23:52 ` [Bug debug/29614] [4.2 " sje at gcc dot gnu dot org
2007-03-05 23:56 ` 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=20061221232044.6915.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).