From: Ian Lance Taylor <iant@google.com>
To: morrell@alumni.ucsd.edu
Cc: gcc-help@gcc.gnu.org
Subject: Re: temp preprocessed filename
Date: Sun, 28 Feb 2010 04:10:00 -0000 [thread overview]
Message-ID: <mcrocjauwry.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <876592.38804.qm@web112615.mail.gq1.yahoo.com> (Michael Morrell's message of "Fri\, 26 Feb 2010 14\:20\:41 -0800 \(PST\)")
Michael Morrell <morrell@alumni.ucsd.edu> writes:
> I'm tracking down some differences in the object files from ostensibly the same compilation flags of the same input. I've got two .o files that should be the same, but when I run:
>
> readelf -wl <object file> | grep ii
>
> to see the debug.line info, I see a difference. The filename that is shown
> is of the form <basename>.tmp,<hostname>.<number>.ii
>
> and <number> is different. I've looked through the source and can't find
> where that filename is generated. I want to know why <number> would change
> and how to prevent it from doing so.
>
> Can anyone point me in the right direction?
I think you can get names of that sort when using distcc and/or
ccache. Are you using either of those? Check the exact path of the
compiler.
Ian
next prev parent reply other threads:[~2010-02-27 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 11:31 Michael Morrell
2010-02-28 4:10 ` Ian Lance Taylor [this message]
2010-02-28 21:34 ` Michael Morrell
2010-03-01 18:26 ` Ian Lance Taylor
2010-03-02 21:13 ` Michael Morrell
2010-03-03 9:05 ` Cedric Roux
2010-03-03 9:35 ` Cedric Roux
2010-03-02 22:05 ` Michael Morrell
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=mcrocjauwry.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=morrell@alumni.ucsd.edu \
/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).