From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Simon Baldwin <simonb@google.com>
Cc: <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>,
Michael Matz <matz@suse.de>, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Reproducible gcc builds, gfortran, and -grecord-gcc-switches
Date: Fri, 24 Aug 2012 14:48:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1208241447560.24652@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAPTY64rMyTTZGP7A16PbOi8t6E5hjnEZCtc4naiLDG_F0wM4Hg@mail.gmail.com>
On Fri, 24 Aug 2012, Simon Baldwin wrote:
> gcc/ChangeLog
> 2012-08-24 Simon Baldwin <simonb@google.com>
>
> * dwarf2out.c (gen_producer_string): Omit command line switch if
> CL_NO_DWARF_RECORD flag set.
> * opts.h (CL_NO_DWARF_RECORD): New.
> * opt-functions.awk (switch_flags): Add NoDWARFRecord.
> * doc/options.texi: Document NoDWARFRecord option flag.
>
> gcc/fortran/ChangeLog
> 2012-08-24 Simon Baldwin <simonb@google.com>
>
> * lang.opt (-cpp=): Mark flag NoDWARFRecord.
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2012-08-24 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPTY64p0=m3O6TOfPf1w1rtF944gHe_ODOsH+Ryx-tdTupVzUA@mail.gmail.com>
[not found] ` <alpine.LNX.2.00.1208160912270.2871@gerinyyl.fvgr>
[not found] ` <CAPTY64ofrdhFVrYNJcHhyrA3J7vpZ=Y6EPrdoWJEwsv3tm3xyw@mail.gmail.com>
[not found] ` <alpine.LNX.2.00.1208161634250.2706@wotan.suse.de>
2012-08-16 16:59 ` Simon Baldwin
2012-08-16 19:34 ` Jakub Jelinek
2012-08-17 9:46 ` Simon Baldwin
2012-08-17 14:56 ` Joseph S. Myers
2012-08-20 14:30 ` Simon Baldwin
2012-08-20 14:45 ` Joseph S. Myers
2012-08-21 12:20 ` Simon Baldwin
2012-08-21 15:18 ` Joseph S. Myers
2012-08-24 11:09 ` Simon Baldwin
2012-08-24 14:48 ` Joseph S. Myers [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=Pine.LNX.4.64.1208241447560.24652@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=matz@suse.de \
--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).