From: Basile Starynkevitch <basile@starynkevitch.net>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: hash signature of cc1 etc....?
Date: Sat, 23 Jul 2011 15:51:00 -0000 [thread overview]
Message-ID: <20110723074553.1a86dfc31de61a4c46bccf53@starynkevitch.net> (raw)
In-Reply-To: <mcrlivqq817.fsf@coign.corp.google.com>
On Fri, 22 Jul 2011 15:12:36 -0700
Ian Lance Taylor <iant@google.com> wrote:
> Basile Starynkevitch <basile@starynkevitch.net> writes:
>
> > Should we add an option to the gcc driver which would print such checksums?
>
> I'm not quite sure what checksums you want.
>
> Suppose you just do
>
> md5sum `gcc --print-file-name=cc1`
>
> ?
>
> That will give you a checksum without gcc going to the trouble of
> generating it.
What about the other files. (lto1, cc1plus...). On my Debian/Sid,
% gcc --print-file-name=cc1
/usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/cc1
But
% ls -F /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/
32/ crtprec80.o libgcj-tools.so@ libquadmath.a
cc1* ecj1* libgcj.so@ libquadmath.so@
cc1plus* gengtype* libgcj.spec libssp_nonshared.a
collect2* gtype.state libgcj_bc.so libstdc++.a
crtbegin.o include/ libgcov.a libstdc++.so@
crtbeginS.o include-fixed/ libgij.so@ libsupc++.a
crtbeginT.o jc1* libgomp.a lto-wrapper*
crtend.o jvgenmain* libgomp.so@ lto1*
crtendS.o libgcc.a libgomp.spec plugin/
crtfastmath.o libgcc_eh.a liblto_plugin.so@
crtprec32.o libgcc_s.so@ liblto_plugin.so.0@
crtprec64.o libgcc_s_32.so@ liblto_plugin.so.0.0.0
How can I know which of the above files have some influence on the behavior of GCC
plugins? (This is not true of all, crtbegin.o don't, and I would think that gengtype
don't neither, because I believe that its observable behavior changes only from 4.6 to
4.7, but not much from 4.6.0 to 4.6.1).
I was suggesting adding some way to get the checksums of only the relevant files.
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
next prev parent reply other threads:[~2011-07-23 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 18:16 Basile Starynkevitch
2011-07-22 22:31 ` Ian Lance Taylor
2011-07-23 15:51 ` Basile Starynkevitch [this message]
2011-07-25 20:26 ` Romain Geissler
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=20110723074553.1a86dfc31de61a4c46bccf53@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).