public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mrs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/46749] gcc.dg/debug/pr41893-1.c -gdwarf-2 testsuite failures on darwin
Date: Fri, 03 Dec 2010 00:26:00 -0000 [thread overview]
Message-ID: <bug-46749-4-cB973RXBdq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46749-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46749
mrs@gcc.gnu.org <mrs at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mrs at gcc dot gnu.org
--- Comment #24 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2010-12-03 00:26:37 UTC ---
The lto people need to engineer a design in which the debug information is left
around in .o files, and those files are read at the very last step in a link,
to collect the debug information from them and persist that information into
the filesystem. They are removing .o files before the end of the final link.
To the extent those files have debug information in them, this can't work.
I could not find the last invocation of gcc that fails. If someone could point
that out, I might be able to suggest a work around that just disappears debug
information until such time as the first bug is fixed. Essentially, you can
remove -g* from that line and disappear the collection of the debug
information. Another solution would be to not have any .c, .cc, .C, .cpp, .cp,
.c++, .cxx, .CPP, .m, .mm, .f, or .s files on that line.
next prev parent reply other threads:[~2010-12-03 0:26 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 17:43 [Bug debug/46749] New: " howarth at nitro dot med.uc.edu
2010-12-01 17:50 ` [Bug debug/46749] " howarth at nitro dot med.uc.edu
2010-12-01 18:05 ` howarth at nitro dot med.uc.edu
2010-12-01 18:44 ` rguenth at gcc dot gnu.org
2010-12-01 20:31 ` howarth at nitro dot med.uc.edu
2010-12-01 20:31 ` howarth at nitro dot med.uc.edu
2010-12-01 20:33 ` howarth at nitro dot med.uc.edu
2010-12-01 20:35 ` howarth at nitro dot med.uc.edu
2010-12-01 20:38 ` rguenth at gcc dot gnu.org
2010-12-01 20:46 ` iains at gcc dot gnu.org
2010-12-01 20:50 ` rguenth at gcc dot gnu.org
2010-12-01 20:59 ` howarth at nitro dot med.uc.edu
2010-12-01 21:11 ` iains at gcc dot gnu.org
2010-12-01 21:21 ` iains at gcc dot gnu.org
2010-12-01 21:24 ` rguenth at gcc dot gnu.org
2010-12-01 21:34 ` iains at gcc dot gnu.org
2010-12-01 21:51 ` rguenther at suse dot de
2010-12-01 21:53 ` iains at gcc dot gnu.org
2010-12-01 22:06 ` iains at gcc dot gnu.org
2010-12-02 8:53 ` rguenther at suse dot de
2010-12-02 9:10 ` iains at gcc dot gnu.org
2010-12-02 9:51 ` rguenther at suse dot de
2010-12-02 10:10 ` iains at gcc dot gnu.org
2010-12-02 10:14 ` iains at gcc dot gnu.org
2010-12-03 0:26 ` mrs at gcc dot gnu.org [this message]
2010-12-03 10:48 ` rguenther at suse dot de
2010-12-03 10:51 ` rguenther at suse dot de
2010-12-03 11:30 ` iains at gcc dot gnu.org
2010-12-03 12:11 ` iains at gcc dot gnu.org
2010-12-03 23:13 ` mikestump at comcast dot net
2010-12-03 23:21 ` rguenther at suse dot de
2010-12-04 0:18 ` mikestump at comcast dot net
2010-12-04 2:11 ` howarth at nitro dot med.uc.edu
2010-12-04 3:19 ` howarth at nitro dot med.uc.edu
2010-12-04 10:28 ` rguenther at suse dot de
2010-12-05 21:13 ` mikestump at comcast dot net
2010-12-05 21:57 ` rguenth at gcc dot gnu.org
2010-12-07 0:26 ` mrs at gcc dot gnu.org
2010-12-07 0:34 ` mrs at gcc dot gnu.org
2010-12-07 9:47 ` rguenth at gcc dot gnu.org
2010-12-07 13:21 ` joseph at codesourcery dot com
2010-12-07 16:34 ` mrs at gcc dot gnu.org
2010-12-07 16:42 ` mikestump at comcast dot net
2010-12-08 20:11 ` mrs at gcc dot gnu.org
2010-12-08 23:13 ` mrs at gcc dot gnu.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=bug-46749-4-cB973RXBdq@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).