From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: David T-G <davidtg@justpickone.org>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: why would two copies of gcc-2.95.2 yield different output?
Date: Wed, 12 Jun 2002 20:17:00 -0000 [thread overview]
Message-ID: <20020613131716.B3069@hg.cs.mu.oz.au> (raw)
In-Reply-To: <20020612190043.GZ17198@justpickone.org>; from davidtg@justpickone.org on Wed, Jun 12, 2002 at 02:00:43PM -0500
On 12-Jun-2002, David T-G <davidtg@justpickone.org> wrote:
> Is there perhaps a way for a mere mortal to reverse-engineer the binaries
> and see what the differences are?
Use objdump (from the GNU binutils package).
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
next prev parent reply other threads:[~2002-06-13 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 12:00 David T-G
2002-06-12 20:17 ` Fergus Henderson [this message]
2002-06-13 6:33 ` David T-G
[not found] <616BE6A276E3714788D2AC35C40CD18D69DB0E@whale.softwire.co.uk>
2002-06-13 3:16 ` Rupert Wood
2002-06-13 6:40 ` David T-G
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=20020613131716.B3069@hg.cs.mu.oz.au \
--to=fjh@cs.mu.oz.au \
--cc=davidtg@justpickone.org \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@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).