jkmcnk / sx-gcc

The GNU Compiler Collection port to NEC SX CPU architecture.
GNU General Public License v2.0
0 stars 2 forks source link

after executing the "strip" command, the timestamp field in object file becomes 0 #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. strip-new <path-to-the-object-file-to-strip>
2. examine the stripped object file with HEX editor. You will see that the
bytes 8-11 are all null.

I looks like the "coff_write_object_contents" contains the
"internal_f.f_timdat = 0;" line (somewhere around line 3767) which always
sets timestamp to 0. Between that and the actual printout to the file,
there is no function that would set the timestamp.

We should probably check with the "binutils" people what is the reason for
this...

Original issue reported on code.google.com by nou...@gmail.com on 13 Aug 2008 at 9:21

GoogleCodeExporter commented 8 years ago

Original comment by nou...@gmail.com on 14 Aug 2008 at 8:17

GoogleCodeExporter commented 8 years ago

Original comment by nou...@gmail.com on 14 Aug 2008 at 8:55

GoogleCodeExporter commented 8 years ago

Original comment by nou...@gmail.com on 14 Aug 2008 at 11:25

GoogleCodeExporter commented 8 years ago
well, the binutils folks clearly state in the comment just above that line that:

  /* We will NOT put a fucking timestamp in the header here. Every time you
     put it back, I will come in and take it out again.  I'm sorry.  This
     field does not belong here.  We fill it with a 0 so it compares the
     same but is not a reasonable time. -- gnu@cygnus.com  */

so we will NOT put a fucking timestamp there either. who cares, anyway.

Original comment by jmoc...@gmail.com on 9 Dec 2008 at 4:15