This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Allow embedded timestamps by C/C++ macros to be set externally
- From: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- To: Dhole <dhole at openmailbox dot org>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 30 Jun 2015 18:23:30 +0200
- Subject: Re: [PATCH] Allow embedded timestamps by C/C++ macros to be set externally
- Authentication-results: sourceware.org; auth=none
- References: <55929721 dot 4020400 at openmailbox dot org> <5592AB0D dot 5000501 at gmail dot com> <5592AC51 dot 5040007 at gmail dot com> <5592B356 dot 3080601 at openmailbox dot org>
On 30 June 2015 at 17:18, Dhole <email@example.com> wrote:
> In the debian reproducible builds project we have considered several
> options to address this issue. We considered redefining the __DATE__ and
> __TIME__ defines by command line flags passed to gcc, but as you say,
> that triggers warnings, which could become errors when building with
> -Werror and thus may require manual intervention on many packages.
Well, it would require adding -Wno-something (-Wno-reproducible?
-Wno-unreproducible? or perhaps simply -freproducible? ) to some
CFLAGS/CXXFLAGS. Is that too much manual intervention? (I'm asking
sincerely, perhaps indeed it is).
This could be a big hammer option that simply disables any warning
that is not relevant for reproducible builds (the default being
-Wsomething), for example avoid emitting --Wbuiltin-macro-redefined
warnings in the specific cases of __TIME__ and __DATE. Just an idea,
the maintainers would need to say if they would accept such an option.