[PATCH] libgo, libstdc++: Regenerate GCC_CHECK_ASSEMBLER_HWCAP users

[PATCH] libgo, libstdc++: Regenerate GCC_CHECK_ASSEMBLER_HWCAP users

[Rainer Orth]

After

Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Thu Nov 30 10:06:23 2023 +0100

    libiberty: Disable hwcaps for sha1.o

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.

This patch regenerates the other users of the GCC_CHECK_ASSEMBLER_HWCAP
macro.  No functional changes.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


2023-11-30  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

	libgo:
	* configure: Regenerate.

	libstdc++-v3:
	* configure: Regenerate.

Re: [PATCH] libgo, libstdc++: Regenerate GCC_CHECK_ASSEMBLER_HWCAP users

[Ian Lance Taylor]

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.

Ian

Re: [PATCH] libgo, libstdc++: Regenerate GCC_CHECK_ASSEMBLER_HWCAP users

[Ian Lance Taylor]

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.

Ian

Re: [PATCH] libgo, libstdc++: Regenerate GCC_CHECK_ASSEMBLER_HWCAP users

[Rainer Orth]

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