From: Joel Brobecker <brobecker@adacore.com>
To: John Gilmore <gnu@toad.com>
Cc: Martin Runge <martin.runge@web.de>,
gdb@sourceware.org, Martin Runge <martin.runge@rohde-schwarz.com>
Subject: Re: RFC: include mod time and size in DWARF file name table
Date: Sun, 13 Jan 2013 05:54:00 -0000 [thread overview]
Message-ID: <20130113055406.GX3567@adacore.com> (raw)
In-Reply-To: <201301130519.r0D5JQJJ016059@new.toad.com>
> Yes. The big problem with this approach is that you can never compile
> the same source code files to produce the same binary code files.
[snip]
I can also confirm that he have had many reports about this as well.
--
Joel
next prev parent reply other threads:[~2013-01-13 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 13:24 Martin Runge
2013-01-13 4:19 ` John Gilmore
2013-01-13 5:54 ` Joel Brobecker [this message]
2013-01-14 12:31 ` Martin Runge
2013-01-15 17:51 ` Tom Tromey
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=20130113055406.GX3567@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=martin.runge@rohde-schwarz.com \
--cc=martin.runge@web.de \
/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