From: Diego Novillo <dnovillo@google.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: Simon Baldwin <simonb@google.com>, gfortran <fortran@gcc.gnu.org>,
gcc-patches@gcc.gnu.org
Subject: Re: [Trunk/GCC 4.6] Re: [google] Omit date from Fortran .mod files for reproducible builds
Date: Fri, 16 Sep 2011 19:07:00 -0000 [thread overview]
Message-ID: <CAD_=9DQJx=m23GzQGy3iCQu8g+q=d9kTR857mD2z6gi-XaAbwQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikvVqV2hSvu-bNBFk+FZDDH8Yn7Y-dCYT23pQyj@mail.gmail.com>
On Fri, Jan 28, 2011 at 13:00, Diego Novillo <dnovillo@google.com> wrote:
> On Fri, Jan 28, 2011 at 06:19, Tobias Burnus <burnus@net-b.de> wrote:
>> We (Janne and I) think this patch can also be applied to the GCC 4.6 trunk;
>> as the date is never read there is also no .mod ABI issue.
>>
>> I assume that there are no copyright issues.
>
> There aren't. Google has signed a blanket copyright assignment with
> the FSF. Any patch coming from a google.com address is covered.
>
> I'll mark this patch for trunk. Thanks.
Tobias, I'm planning to apply this (old) patch to trunk. Still OK?
I've re-bootstrapped on x86_64. No new failures.
Thanks. Diego.
2011-09-16 Simon Baldwin <simonb@google.com>
* module.c (gfc_dump_module): Omit timestamp from output.
diff --git a/gcc/fortran/module.c b/gcc/fortran/module.c
index 4250a17..b29ba4b 100644
--- a/gcc/fortran/module.c
+++ b/gcc/fortran/module.c
@@ -5178,8 +5178,7 @@ void
gfc_dump_module (const char *name, int dump_flag)
{
int n;
- char *filename, *filename_tmp, *p;
- time_t now;
+ char *filename, *filename_tmp;
fpos_t md5_pos;
unsigned char md5_new[16], md5_old[16];
@@ -5221,13 +5220,8 @@ gfc_dump_module (const char *name, int dump_flag)
filename_tmp, xstrerror (errno));
/* Write the header, including space reserved for the MD5 sum. */
- now = time (NULL);
- p = ctime (&now);
-
- *strchr (p, '\n') = '\0';
-
- fprintf (module_fp, "GFORTRAN module version '%s' created from %s on %s\n"
- "MD5:", MOD_VERSION, gfc_source_file, p);
+ fprintf (module_fp, "GFORTRAN module version '%s' created from %s\n"
+ "MD5:", MOD_VERSION, gfc_source_file);
fgetpos (module_fp, &md5_pos);
fputs ("00000000000000000000000000000000 -- "
"If you edit this, you'll get what you deserve.\n\n", module_fp);
next prev parent reply other threads:[~2011-09-16 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 14:41 Simon Baldwin
2011-01-27 14:53 ` Diego Novillo
2011-01-28 13:14 ` [Trunk/GCC 4.6] " Tobias Burnus
2011-01-28 19:06 ` Diego Novillo
2011-09-16 19:07 ` Diego Novillo [this message]
2011-09-20 11:12 ` Janne Blomqvist
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='CAD_=9DQJx=m23GzQGy3iCQu8g+q=d9kTR857mD2z6gi-XaAbwQ@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=simonb@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).