From: Geoff Keating <geoffk@geoffk.org>
To: nelcomp@attglobal.net
Cc: gcc@gcc.gnu.org
Subject: Re: Building unique object files and binaries
Date: Tue, 13 Nov 2001 11:48:00 -0000 [thread overview]
Message-ID: <jm3d364ige.fsf@geoffk.org> (raw)
In-Reply-To: "Ian S. Nelson"'s message of "Thu, 22 Nov 2001 09:57:27 -0700"
"Ian S. Nelson" <nelcomp@attglobal.net> writes:
> I'm sure this has been discussed before but is there a patch or any
> desire to modify gcc to add timestamping and some sort of unique
> identifier to each object file output (or maybe this is a binutils
> thing) so that they are all different and unique for the purpose of
> identification?
There is a strong desire to _remove_ timestamps and unique identifiers
from object files, so that they can be compared. A very useful part
of GCC's testing relies on object files being able to be compared.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next prev parent reply other threads:[~2001-11-22 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 10:54 Ian S. Nelson
2001-11-13 11:48 ` Geoff Keating [this message]
2001-11-13 12:57 ` Florian Weimer
2001-11-13 14:40 ` Adrian von Bidder
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=jm3d364ige.fsf@geoffk.org \
--to=geoffk@geoffk.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@redhat.com \
--cc=nelcomp@attglobal.net \
/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).