From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Ian Lance Taylor <iant@golang.org>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libgo, libstdc++: Regenerate GCC_CHECK_ASSEMBLER_HWCAP users
Date: Fri, 01 Dec 2023 10:02:57 +0100 [thread overview]
Message-ID: <yddo7fauwfy.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAKOQZ8x7bpdVZxQod5i921RNLjTPF018epz-fYFo_y8g861sYQ@mail.gmail.com> (Ian Lance Taylor's message of "Thu, 30 Nov 2023 13:24:53 -0800")
Hi Ian,
> On Thu, Nov 30, 2023 at 11:46 AM Ian Lance Taylor <iant@golang.org> wrote:
>>
>> On Thu, Nov 30, 2023 at 1:30 AM Rainer Orth <ro@cebitec.uni-bielefeld.de>
>> wrote:
>> >
>> > the gcc-autoregen bot correctly complained that the libgo and libstdc++
>> > configure scripts hadn't been regenerated. I'd have commited the
>> > following as obvious (just whitespace change), but since libgo is
>> > imported from upstream, I'm uncertain how best to handle that part.
>>
>> I can update libgo/configure upstream, but first I'd like to
>> understand the change in git revision
>> 6a6d3817afa02bbcd2388c8e005da6faf88932f1, which seems unnecessary.
>> Asked in https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638814.html.
>
> OK, fixed now in the GCC repo.
thanks for taking care of this. I've now regenerated the libstdc++
configure script, too, which should silence the gcc-autoregen bot.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2023-12-01 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 9:30 Rainer Orth
2023-11-30 19:46 ` Ian Lance Taylor
2023-11-30 21:24 ` Ian Lance Taylor
2023-12-01 9:02 ` Rainer Orth [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=yddo7fauwfy.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=libstdc++@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).