public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/32998] -frecord-gcc-switches issues
Date: Mon, 06 Aug 2007 19:19:00 -0000 [thread overview]
Message-ID: <20070806191931.1194.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32998-87@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from roland at redhat dot com 2007-08-06 19:19 -------
Absolute file names are a very bad idea. That makes for gratuitous differences
in builds due to the build or source directory name, i.e. unrepeatable builds.
The names in .debug_line and .debug_info are already expected by
post-processing tools and taken care of. Do not add another location in the
object that might contain absolute file names.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32998
next prev parent reply other threads:[~2007-08-06 19:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 21:17 [Bug other/32998] New: " jakub at gcc dot gnu dot org
2007-08-06 8:12 ` [Bug other/32998] " nickc at redhat dot com
2007-08-06 16:17 ` bkoz at gcc dot gnu dot org
2007-08-06 19:19 ` roland at redhat dot com [this message]
2007-08-07 8:11 ` nickc at redhat dot com
2007-08-07 8:25 ` nickc at redhat dot com
2010-06-20 21:03 ` jsm28 at gcc dot gnu dot org
2010-06-20 21:05 ` jsm28 at gcc dot gnu dot org
2010-06-20 21:20 ` manu at gcc dot gnu dot org
[not found] <bug-32998-4@http.gcc.gnu.org/bugzilla/>
2010-10-02 16:06 ` jan.kratochvil at redhat dot com
2010-10-05 0:42 ` roland at redhat dot com
2010-10-05 9:48 ` jakub at gcc dot gnu.org
2010-10-05 19:54 ` roland at redhat dot com
2011-04-22 18:49 ` jan.kratochvil at redhat dot com
2011-07-12 16:26 ` jakub at gcc dot gnu.org
2011-07-22 20:04 ` jakub at gcc dot gnu.org
2012-06-14 9:22 ` philomath868 at gmail dot com
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=20070806191931.1194.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).