From: Iain Sandoe <idsandoe@googlemail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Jakub Jelinek via Gcc <gcc@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: gcc/DATESTAMP not updated any longer
Date: Fri, 6 Nov 2020 20:08:27 +0000 [thread overview]
Message-ID: <A708D72B-0A57-4A80-A8C7-3E3AABAE0A8E@googlemail.com> (raw)
In-Reply-To: <20201106195903.GP3788@tucnak>
Jakub Jelinek via Gcc <gcc@gcc.gnu.org> wrote:
> On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote:
>>> Darwin: Darwin 20 is to be macOS 11 (Big Sur).
>>> So, I'm afraid it must fail or bypass this code path somewhere earlier
>>> in the hooks.
>>
>> Is that maybe already known to the repo when it is on some rebased user
>> branch?
>
> I don't think so.
That commit was only present on a local branch, so not “known” to the repo,
for sure.
Iain
> I think I'll work with Martin early next week to think about further spots
> to add logging, so we narrow down where it is still called and where it
> isn't.
> But we really don't have a reliable reproducer, commit this and it won't
> show up.
>
> Jakub
next prev parent reply other threads:[~2020-11-06 20:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 19:14 Rainer Orth
2020-11-02 19:43 ` Jakub Jelinek
2020-11-02 20:37 ` Martin Liška
2020-11-02 20:58 ` Jakub Jelinek
2020-11-03 18:26 ` Joseph Myers
2020-11-06 19:45 ` Jakub Jelinek
2020-11-06 19:56 ` Richard Biener
2020-11-06 19:59 ` Jakub Jelinek
2020-11-06 20:08 ` Iain Sandoe [this message]
2020-11-08 9:55 ` Iain Sandoe
2020-11-09 7:57 ` Martin Liška
2020-11-09 22:09 ` Jakub Jelinek
2020-11-10 8:23 ` Martin Liška
2020-11-13 9:57 ` Jakub Jelinek
2020-12-11 13:17 ` Rainer Orth
2020-12-11 18:04 ` Martin Liška
2020-12-11 18:26 ` Jakub Jelinek
2020-12-14 8:59 ` Martin Liška
2020-12-14 9:05 ` Jakub Jelinek
2020-12-14 9:21 ` Martin Liška
2020-12-14 9:23 ` Jakub Jelinek
2020-12-14 9:32 ` Martin Liška
2020-12-14 10:02 ` Andreas Schwab
2020-12-14 10:18 ` Jakub Jelinek
2020-12-15 0:04 ` Joseph Myers
2020-12-14 23:58 ` Joseph Myers
2020-12-15 8:30 ` Martin Liška
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=A708D72B-0A57-4A80-A8C7-3E3AABAE0A8E@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
--cc=richard.guenther@gmail.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).