public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/61371] cpp: Implement -fno-date-time/-freproducible-dates or similar
Date: Fri, 30 May 2014 15:58:00 -0000 [thread overview]
Message-ID: <bug-61371-4-hayoflbjvz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61371-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61371
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
You can simply redefine them in the command-line:
http://lists.opensuse.org/opensuse-buildservice/2011-04/msg00049.html
isn't that enough?
>From gcc-bugs-return-452871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 30 16:01:26 2014
Return-Path: <gcc-bugs-return-452871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5483 invoked by alias); 30 May 2014 16:01:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5436 invoked by uid 48); 30 May 2014 16:01:22 -0000
From: "crrodriguez at opensuse dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/61371] cpp: Implement -fno-date-time/-freproducible-dates or similar
Date: Fri, 30 May 2014 16:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: crrodriguez at opensuse dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61371-4-o1OvBNuewr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61371-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61371-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg02563.txt.bz2
Content-length: 426
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61371
--- Comment #2 from Cristian Rodríguez <crrodriguez at opensuse dot org> ---
(In reply to Manuel López-Ibáñez from comment #1)
> You can simply redefine them in the command-line:
>
> http://lists.opensuse.org/opensuse-buildservice/2011-04/msg00049.html
>
> isn't that enough?
It would be.. if there wasn't half a ton of packages using -Werror
>From gcc-bugs-return-452872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 30 16:02:07 2014
Return-Path: <gcc-bugs-return-452872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7866 invoked by alias); 30 May 2014 16:02:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7761 invoked by uid 48); 30 May 2014 16:02:04 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/61371] cpp: Implement -fno-date-time/-freproducible-dates or similar
Date: Fri, 30 May 2014 16:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61371-4-YlXyCUjdqp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61371-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61371-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg02564.txt.bz2
Content-length: 304
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida371
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Why don't you poision the use of __DATE__ and __TIME__ in a header file that
you -include to force people not to use use those macros which allows you to
audit the packages in one go.
next parent reply other threads:[~2014-05-30 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-61371-4@http.gcc.gnu.org/bugzilla/>
2014-05-30 15:58 ` manu at gcc dot gnu.org [this message]
2014-05-30 16:02 ` manu at gcc dot gnu.org
2014-05-30 16:21 ` crrodriguez at opensuse dot org
2014-06-02 8:16 ` rguenth at gcc dot gnu.org
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=bug-61371-4-hayoflbjvz@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).