From: llewelly@xmission.com
To: "Crumrine, Ray" <Ray.Crumrine@Glenayre.com>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: Linux gcc compiler output
Date: Tue, 04 May 2004 13:08:00 -0000 [thread overview]
Message-ID: <s3ry8o8fig5.fsf@xmission.xmission.com> (raw)
In-Reply-To: <76D03A0A5583D611B76F0008025853EB1DF9A6@quincy-nt2.quincy.glenayre.com>
"Crumrine, Ray" <Ray.Crumrine@Glenayre.com> writes:
> I'm trying to find out where in the header of the resulting file that is
> created when gcc runs is the date / time of file creation and what format.
> Can anyone help? I'm assuming it's probably there in some binary format. Any
> help is appreciated.
I'm not sure what you are asking. gcc does not normally put a
timestamp in its output.
You can put code like this:
char const* cp= "Date: " __DATE__;
char const* cp2= "Time: " __TIME__;
in your program, and on most systems you can run strings on the
resulting binary, and see something like this:
$ strings a.out | grep 'Date\|Time'
Date: May 4 2004
Time: 07:04:56
If the output is an archive, and you
have gnu binutils, you can use objdump -a to see the dates the
individual members of the archive were added.
That's all I know about.
prev parent reply other threads:[~2004-05-04 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 20:12 Crumrine, Ray
2004-05-04 13:08 ` llewelly [this message]
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=s3ry8o8fig5.fsf@xmission.xmission.com \
--to=llewelly@xmission.com \
--cc=Ray.Crumrine@Glenayre.com \
--cc=gcc-help@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).