From: Christophe Lyon <christophe.lyon@linaro.org>
To: Matthias Klose <doko@ubuntu.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>,
Dhole <dhole@openmailbox.org>,
Eduard Sanou <eduardsanou@openmailbox.org>,
Jakub Jelinek <jakub@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Allow embedded timestamps by C/C++ macros to be set externally (3)
Date: Thu, 02 Jun 2016 13:01:00 -0000 [thread overview]
Message-ID: <CAKdteOY6hTyCRdMLT9XJcDKUu5=KCqWMB9aDFWNbyqYCqG=AGQ@mail.gmail.com> (raw)
In-Reply-To: <574F1483.6030806@ubuntu.com>
On 1 June 2016 at 18:59, Matthias Klose <doko@ubuntu.com> wrote:
> On 01.06.2016 18:29, Bernd Schmidt wrote:
>> On 05/13/2016 07:09 PM, Dhole wrote:
>>> + pfile->source_date_epoch = pfile->cb.get_source_date_epoch(pfile);
>>
>> Space before paren. Ok with that change.
>>
>>> * c-common.h (c_omp_region_type): Remove trailing coma.
>>
>> Also, comma.
>
> committed with these changes.
>
Hi,
Since this was committed, I'm seeing:
- ~random failures of pr61861:
/aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/testsuite/gcc.dg/pr61861.c:22:3:
error: environment variable SOURCE_DATE_EPOCH must expand to a
non-negative integer less than or equal to 253402300799
I've noticed that HJ has reported it on gcc-regressions, too.
It would help if the error message showed the value of SOURCE_DATE_EPOCH :)
next prev parent reply other threads:[~2016-06-02 13:01 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 12:28 Dhole
2016-04-18 13:05 ` Markus Trippelsdorf
2016-05-03 14:44 ` Dhole
2016-05-03 14:53 ` Markus Trippelsdorf
2016-04-25 10:16 ` Bernd Schmidt
2016-04-26 21:29 ` Dhole
2016-04-26 23:33 ` Bernd Schmidt
2016-04-27 15:57 ` Dhole
2016-04-28 9:20 ` Matthias Klose
2016-04-28 9:22 ` Bernd Schmidt
2016-04-28 10:08 ` Jakub Jelinek
2016-04-28 10:31 ` Bernd Schmidt
2016-04-28 10:35 ` Jakub Jelinek
2016-04-28 13:10 ` Bernd Schmidt
2016-04-28 13:14 ` Jakub Jelinek
2016-04-28 18:31 ` Dhole
2016-04-29 7:17 ` Jakub Jelinek
2016-05-05 23:28 ` Eduard Sanou
2016-05-06 6:26 ` Andreas Schwab
2016-05-10 11:14 ` Dhole
2016-05-10 11:24 ` Andreas Schwab
2016-05-10 11:32 ` Bernd Schmidt
2016-05-10 15:51 ` Joseph Myers
2016-05-12 0:38 ` Dhole
2016-05-12 9:17 ` Bernd Schmidt
2016-05-13 17:11 ` Dhole
2016-05-23 23:00 ` Dhole
2016-05-24 16:45 ` Jeff Law
2016-06-01 16:29 ` Bernd Schmidt
2016-06-01 16:59 ` Matthias Klose
2016-06-02 13:01 ` Christophe Lyon [this message]
2016-06-02 13:05 ` Jakub Jelinek
2016-06-02 13:21 ` Christophe Lyon
2016-06-02 13:24 ` Jakub Jelinek
2016-06-02 14:50 ` Christophe Lyon
2016-06-02 15:04 ` Jakub Jelinek
2016-06-02 15:27 ` Bernd Schmidt
2016-06-02 15:30 ` Christophe Lyon
2016-06-02 12:19 ` Fix up dg-set-compiler-env-var Jakub Jelinek
2016-06-02 12:26 ` Bernd Schmidt
2016-06-02 12:33 ` Jakub Jelinek
2016-05-05 23:39 ` Allow embedded timestamps by C/C++ macros to be set externally (3) Dhole
2016-05-09 10:24 ` Bernd Schmidt
2016-05-09 10:38 ` Bernd Schmidt
2016-05-09 10:42 ` Jakub Jelinek
2016-05-09 11:01 ` Bernd Schmidt
2016-05-10 11:18 ` Dhole
2016-04-28 18:57 ` Martin Sebor
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='CAKdteOY6hTyCRdMLT9XJcDKUu5=KCqWMB9aDFWNbyqYCqG=AGQ@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=bschmidt@redhat.com \
--cc=dhole@openmailbox.org \
--cc=doko@ubuntu.com \
--cc=eduardsanou@openmailbox.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).