[PATCH] testsuite: Skip target not support -pthread [pr104676].

The "ftree-parallelize-loops=" imply -pthread option in gcc/gcc.cc, some target are not support pthread like elf target use newlib, and will get an error: "*-*-elf-gcc: error: unrecognized command-line option '-pthread'" so we add an additional condition "{target pthread}" to make sure the dg-add

[COMMITTED] readings.html: Add replacement URL for CRIS Programmer's Manual

Also available through the wayback machine, but only a valid currently-working URL is appropriate on that page, IMHO. Thanks to Paul Koning for finding it. --- htdocs/readings.html | 1 + 1 file changed, 1 insertion(+) diff --git a/htdocs/readings.html b/htdocs/readings.html index 2467945b1cb6..

Re: [PATCH] mksigtab.sh: Add support for musl libc

On Fri, Apr 15, 2022 at 6:38 AM Sören Tempel wrote: > > Attached are two small git-format-patch(1) files which add support for > musl libc to gofrontend's mksigtab.sh script. They address the following > issues: > > * Signal 34 is special on musl and is used internally for > setg

[PATCH v2] c++: Fall through for arrays of T vs T cv [PR104996]

If two arrays do not have the exact same element type including qualification, this could be e.g. f(int (&&)[]) vs. f(int const (&)[]), which can still be distinguished by the lvalue-rvalue tiebreaker. By tightening this branch (in accordance with the letter of the Standard) we fall through to

[ping][PATCH 0/8][RFC] Support BTF decl_tag and type_tag annotations

Gentle ping :) Link: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/592685.html The series adds support for new attribues btf_type_tag and btf_decl_tag, for recording arbitrary string tags in DWARF and BTF debug info. The feature is to support kernel use cases. Thanks, David On 4/1/22

Re: [PATCH] libstdc++: Micro-optimize __from_chars_pow2_base

On Mon, 18 Apr 2022, 15:39 Patrick Palka via Libstdc++, < libstd...@gcc.gnu.org> wrote: > At the first iteration of __from_chars_pow2_base's main loop, we need > to remember the value of the leading significant digit for sake of the > overflow check at the end of the function (for bases other than

Re: [AArch64] PR105162: emit barrier for __sync and __atomic builtins on CPUs without LSE

Hi, Wilco pointed out in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105162#c7? that "Only __sync needs the extra full barrier, but __atomic does not." The attached patch does that by adding out-of-line functions for MEMMODEL_SYNC_*. Those new functions contain a barrier on the path without

[PATCH v3 1/2] rs6000: Move g++.dg powerpc PR tests to g++.target

Also adjust DejaGnu directives, as specifically requiring "powerpc*-*-*" is no longer required. 2021-04-18 Paul A. Clarke gcc/testsuite * g++.dg/pr65240.h: Move to g++.target/powerpc. * g++.dg/pr93974.C: Likewise. * g++.dg/pr65240-1.C: Move to g++.target/powerpc, adjust

[PATCH v3 2/2] rs6000: Remove a few needless 'lp64' contraints.

A few tests need not be restricted to 'lp64', so remove the restriction. A few of those need a simple change to the DejaGnu directives to suppress '-mcmodel' flags for '-m32'. 2022-04-18 Paul A. Clarke gcc/testsuite * g++.target/powerpc/pr65240-1.C: Adjust DejaGnu directives.

[PATCH v3 0/2] rs6000: Move g++.dg powerpc tests to g++.target

v3: moved "not tested on Darwin" changes into 1/2, where they belong. v2: - v1 patches 1/3 and 2/3 have been merged after reviews / approval. - Previous 3/3 is now 1/2, and new 2/2 is per review from Segher... Some tests in g++.dg are target-specific for powerpc. Move those to g++.target/powerpc.

Re: [PATCH] doc/invoke.texi: CRIS: Remove references to cris-axis-linux-gnu

> From: Hans-Peter Nilsson > gcc: > * doc/install.texi : Remove references to removed websites and > adjust for cris-*-elf being the only remaining toolchain. Oops, cutnpasto for the ChangeLog entry. :( This one fits better: * doc/invoke.texi : Remove references to options f

[PATCH] doc/invoke.texi: CRIS: Remove references to cris-axis-linux-gnu

I'm about to commit this to master. I'd like to also install this on the gcc-11 branch. Ok? -- 8< -- ...and related options. These stale bits were overlooked when support for "Linux/GNU" and CRIS v32 was removed, before the gcc-11 release. Resulting pdf, html and info inspected for sanity. g

[PATCH v2 1/2] rs6000: Move g++.dg powerpc PR tests to g++.target

Also adjust DejaGnu directives, as specifically requiring "powerpc*-*-*" is no longer required. 2021-04-18 Paul A. Clarke gcc/testsuite * g++.dg/pr65240.h: Move to g++.target/powerpc. * g++.dg/pr93974.C: Likewise. * g++.dg/pr65240-1.C: Move to g++.target/powerpc, adjust

[PATCH v2 2/2] rs6000: Remove a few needless 'lp64' contraints.

A few tests need not be restricted to 'lp64', so remove the restriction. A few of those need a simple change to the DejaGnu directives to suppress '-mcmodel' flags for '-m32'. 2022-04-18 Paul A. Clarke gcc/testsuite * g++.target/powerpc/pr65240-1.C: Adjust DejaGnu directives.

[PATCH v2 0/2] rs6000: Move g++.dg powerpc tests to g++.target

V1 patches 1/3 and 2/3 have been merged after reviews / approval. Previous 3/3 is now 1/2, and new 2/2 is per review from Segher... Some tests in g++.dg are target-specific for powerpc. Move those to g++.target/powerpc. Update the DejaGnu directives as needed, since the target restriction is perh

[PATCH] doc/install.texi: CRIS: Remove gone websites. Adjust CRIS targets

I'm about to commit this to master. I'd like to also install this on the gcc-11 branch. Ok? -- 8< -- That is, support for cris-linux-gnu was removed in gcc-11, but install.texi wasn't adjusted accordingly. Also, unfortunately the developer-related sites are gone with no replacements. And, CRI

[COMMITTED] readings.html: developer.axis.com is gone, remove

Unfortunately I know of no replacement. --- htdocs/readings.html | 1 - 1 file changed, 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 8689eab8b2d1..2467945b1cb6 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -118,7 +118,6 @@ names. Manufacturer:

[PATCH] c++, coroutines: Improve check for throwing final await [PR104051].

We check that the final_suspend () method returns a sane type (i.e. a class or structure) but, unfortunately, that check has to be later than the one for a throwing case. If the user returns some nonsensical type from the method, we need to handle that in the checking for noexcept. tested on x86_

[PATCH] libstdc++: Micro-optimize __from_chars_pow2_base

At the first iteration of __from_chars_pow2_base's main loop, we need to remember the value of the leading significant digit for sake of the overflow check at the end of the function (for bases other than 2). This patch manually unrolls this first iteration so as to not encumber the entire loop wi

[PATCH] c++, coroutines: Account for overloaded promise return_value() [PR105301].

Whether it was intended or not, it is possible to define a coroutine promise with multiple return_value() methods [which need not even have the same type]. We were not accounting for this possibility in the check to see whether both return_value and return_void are specifier (which is prohibited b

[PATCH] c++, coroutines: Make sure our temporaries are in a bind expr [PR105287]

There are a few cases where we can generate a temporary that does not need to be added to the coroutine frame (i.e. these are genuinely ephemeral). The intent was that unnamed temporaries should not be 'promoted' to coroutine frame entries. However there was a thinko and these were not actually e

Re: [PATCH] c++: Fix up CONSTRUCTOR_PLACEHOLDER_BOUNDARY handling [PR105256]

On Sun, Apr 17, 2022 at 6:24 PM Jason Merrill wrote: > > On 4/15/22 07:22, Jakub Jelinek wrote: > > Hi! > > > > The CONSTRUCTOR_PLACEHOLDER_BOUNDARY bit is supposed to separate > > PLACEHOLDER_EXPRs that should be replaced by one object or subobjects of it > > (variable, TARGET_EXPR slot, ...) fro