From: Danny Smith <danny_smith_0000@yahoo.co.nz>
To: christian.joensson@gmail.com
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: Problems bootstrapping mainline on cygwin: warning: ./cc1-checksum.o ./cc1obj-checksum.o ./cc1plus-checksum.o libgcc/_chkstk.o differ
Date: Sun, 07 Aug 2005 08:12:00 -0000 [thread overview]
Message-ID: <20050807081247.44610.qmail@web50909.mail.yahoo.com> (raw)
Christian Joensson wrote
> I haven't bootstrapped gcc on cygwin for a while now... but, using gcc
> cvs trunk LAST_UPDATED: Fri Aug 5 09:05:37 UTC 2005, I get comparison
> warnings...:
> warning: ./cc1-checksum.o differs
> warning: ./cc1obj-checksum.o differs
> warning: ./cc1plus-checksum.o differs
ld inserts an 4 byte timestamp into the "Image File Header" (offset 4
bytes) of pe-coff executables. I believe that genchecksum.c takes that
into account at line 46:
/* Some executable formats have timestamps in the first 16 bytes, yuck. */
if (fseek (f, 16, SEEK_SET) != 0)
But ld also inserts a 4-byte checksum of its own further down, (offset
64 bytes into the Image Optional Header). Changes in timestamps between
stages will cause changes in the Optional Header checksums. GCC's
genchecksum doesn't take that into account.
I'd guess that the checksum diff for libgcc/_chkstk.o is due to
differences in the name of the preprocessor-generated temp *.s
assembly file in .stabstr section
Danny
Send instant messages to your online friends http://au.messenger.yahoo.com
next reply other threads:[~2005-08-07 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 8:12 Danny Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-05 12:16 Christian Joensson
2005-08-05 22:31 ` James E Wilson
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=20050807081247.44610.qmail@web50909.mail.yahoo.com \
--to=danny_smith_0000@yahoo.co.nz \
--cc=christian.joensson@gmail.com \
--cc=dannysmith@users.sourceforge.net \
--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).