From: Richard Earnshaw <rearnsha@arm.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org, Richard.Earnshaw@arm.com
Subject: Re: Object files know where they're built?!?
Date: Sat, 01 Mar 2003 19:11:00 -0000 [thread overview]
Message-ID: <200303011910.h21JAX421934@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Sat, 01 Mar 2003 12:52:18 EST." <20030301175218.GA335@doctormoo>
> Joseph Myers said:
> >dependencies, between all stages, to one invocation of make, but this
> >can't work because each stage needs to be built separately, with the
> >files
> >in the same location (not in the stage subdirectory), for the compare
> >stage to succeed.
>
> I ran into this when I tried to use a different scheme for building
> stage1. I wanted to compare the files produced by my new scheme with
> the files produced by the original. My new scheme built stage1 in a
> different directory (stage1-gcc). Every object file differed at byte 33
> or 34.
>
> I couldn't figure out why.
>
> Do the object files (on i686-pc-linux-gnu) somehow encode their build
> location? This would be stupid, obviously, but if it's true it's true.
> :-) Is there a way to compare the object files without regard to
> spurious differences like this?
Not necessarily, but they do include the location of source and include
files (so that debuggers can find things) -- and most files will include
config.h, insn-flags.h, etc which are put in the build directory.
R.
next prev parent reply other threads:[~2003-03-01 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 17:52 Nathanael Nerode
2003-03-01 19:11 ` Richard Earnshaw [this message]
2003-03-03 10:31 ` Alexandre Oliva
2003-03-02 1:58 Nathanael Nerode
2003-03-02 21:41 Bruce Korb
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=200303011910.h21JAX421934@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@twcny.rr.com \
/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).