[pushed] libgcc, Darwin: From macOS 11, make that the earliest supported.

This has been in use for some time on the Darwin branches, re-tested on x86_64-darwin21 and powerpc64le-linux, pushed to trunk. thanks Iain --- >8 --- For libgcc, we have (so far) supported building a DSO that supports earlier versions of the OS than the target. From macOS 11, there are APIs tha

[pushed] testsuite, coroutines: Add tests for non-supension ramp returns.

Tested on x86_64-darwin, powerpc64le-linux, pushed to trunk, thanks, Iain --- 8< --- Although it is most common for the ramp function to see a return when a coroutine first suspends, there are other possibilities. For example all the awaits could be ready - effectively the coroutine will then r

[PATCH 3/3] gimple: Simplify gimple_seq_nondebug_singleton_p

The implementation of gimple_seq_nondebug_singleton_p was convoluted on how to determine if the sequence was a singleton (which could contain debug statements). This simplifies the function into two calls. One to get the start after all of the debug statements and then check to see if it is at the

[PATCH 1/3] Remove commented out PHI_ARG_DEF macro defition

This was commented out since r0-125500-g80560f9521f81a and a new defition was added at the same time. Let's remove the commented out version. gcc/ChangeLog: * tree-ssa-operands.h (PHI_ARG_DEF): Remove definition. Signed-off-by: Andrew Pinski --- gcc/tree-ssa-operands.h | 3 --- 1 file

[PATCH 2/3] gimple: Remove custom remove_pointer

Since r11-2700-g22dc89f8073cd0, type_traits has been included via system.h so we don't need a custom version for gimple.h. Note a small C++14 cleanup is to use remove_pointer_t directly here instead of remove_pointer::type. bootstrapped and tested on x86_64-linux-gnu gcc/ChangeLog: * gi

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sep 22 2024, Jakub Jelinek wrote: > On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: >> On Sep 22 2024, Mikael Morin wrote: >> >> > @@ -370,7 +370,7 @@ Set the default accessibility of module entities to >> > @code{PRIVATE}. >> > Use-associated entities will not be accessible

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sun, Sep 22, 2024 at 11:47:09PM +0200, Andreas Schwab wrote: > On Sep 22 2024, Jakub Jelinek wrote: > > > On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: > >> On Sep 22 2024, Mikael Morin wrote: > >> > >> > @@ -370,7 +370,7 @@ Set the default accessibility of module entities to

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

Andreas Schwab writes: > On Sep 22 2024, Jakub Jelinek wrote: > >> On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: >>> On Sep 22 2024, Mikael Morin wrote: >>> >>> > @@ -370,7 +370,7 @@ Set the default accessibility of module entities to >>> > @code{PRIVATE}. >>> > Use-associate

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sep 22 2024, Arsen Arsenović wrote: > Andreas Schwab writes: > >> On Sep 22 2024, Jakub Jelinek wrote: >> >>> On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: On Sep 22 2024, Mikael Morin wrote: > @@ -370,7 +370,7 @@ Set the default accessibility of module entiti

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

e 22/09/2024 à 16:27, Jakub Jelinek a écrit : On Sun, Sep 22, 2024 at 04:17:11PM +0200, Mikael Morin wrote: -@opindex @code{std=}@var{std} option +@opindex std=@var{std} option IMHO this one should be just @opindex std=@var{std} The option part is superfluous. Yes, this one looked strange t

[committed] testsuite/gfortran.dg/unsigned_22.f90: Add missing close with delete, PR116701

Committed as pre-approved in the bugzilla PR. Heads-up: I intend to also submit for approval a patch that adds (the equivalent of) ! { dg-final { remote_file target delete "fort.10" } } to all running fortran test-cases that has an open-unit- statement (i.e. can create one of those "anonymous" f

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sep 22 2024, Mikael Morin wrote: > @@ -370,7 +370,7 @@ Set the default accessibility of module entities to > @code{PRIVATE}. > Use-associated entities will not be accessible unless they are explicitly > declared as @code{PUBLIC}. > > -@opindex @code{ffixed-line-length-}@var{n} > +@opindex

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sun, Sep 22, 2024 at 10:52:37PM +0200, Andreas Schwab wrote: > On Sep 22 2024, Mikael Morin wrote: > > > @@ -370,7 +370,7 @@ Set the default accessibility of module entities to > > @code{PRIVATE}. > > Use-associated entities will not be accessible unless they are explicitly > > declared as @

Re: [PATCH v1] libstdc++: Optimize removal from unique assoc containers [PR112934]

Hi Jonathan It seems this patch got stuck, is there any chance it could be ultimately accepted or rejected some time in the future? Regards, Barnabás Pőcze 2024. március 13., szerda 12:43 keltezéssel, Jonathan Wakely írta: > On Mon, 11 Mar 2024 at 23:36, Barnabás Pőcze wrote: > > > > Pre

Re: [PATCH v1] libstdc++: Optimize removal from unique assoc containers [PR112934]

On Sun, 22 Sept 2024 at 20:08, Barnabás Pőcze wrote: > > Hi Jonathan > > > It seems this patch got stuck, is there any chance it could be ultimately > accepted > or rejected some time in the future? Thanks for the reminder, it's still in my TODO list of patches to merge. I'll look at it in the n

[PING] [PATCH] i386: Implement Thread Local Storage on Windows

Hi all, Pinging https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662860.html as it has been buried under several other patches. Any i386 experts here to help me with the patch and commit it once it has been refined? Is the patch ok? best regards, Julian

[PATCH]middle-end: Insert invariant instructions before the gsi [PR116812[

Hi All, The new invariant statements should be inserted before the current statement and not after. This goes fine 99% of the time but when the current statement is a gcond the control flow gets corrupted. Bootstrapped Regtested on aarch64-none-linux-gnu and no issues. Ok for master? Thanks, T

[PATCH v1] RISC-V: RISC-V: Add testcases for form 4 of signed vector SAT_ADD

From: Pan Li Form 4: #define DEF_VEC_SAT_S_ADD_FMT_4(T, UT, MIN, MAX) \ void __attribute__((noinline)) \ vec_sat_s_add_##T##_fmt_4 (T *out, T *op_1, T *op_2, unsigned limit) \ {

Re: LIBGCC14 fails to build on MacOS Sequoia x64

Hi Samuele, The gcc-patches list is for submission and review of patches to GCC. For general help, please use the generic gcc mailing-list (g...@gcc.gnu.org ), and/or file a bug directly at https://gcc.gnu.org/bugzilla/ The issue you’re referring to, a failure to build

[PATCH] libstdc++: Fix race condition in std::ios_base::Init construction [PR111676]

Tested x86_64-linux. -- >8 -- The current implementation of std::ios_base::Init::Init() uses an atomic reference count to ensure that the global iostreams are only initialized once. However, it doesn't ensure that other threads will wait for that initialization to finish before trying to use the

[committed] libstdc++: Fix condition for ranges::copy to use memmove [PR116754]

Tested x86_64-linux. Pushed to trunk. -- >8 -- libstdc++-v3/ChangeLog: PR libstdc++/116754 * include/bits/ranges_algobase.h (__copy_or_move): Fix order of arguments to __memcpyable. --- libstdc++-v3/include/bits/ranges_algobase.h | 2 +- 1 file changed, 1 insertion(+), 1

[committed] libstdc++: Disable std::formatter specialization

Tested x86_64-linux. Pushed to trunk. -- >8 -- I noticed that char8_t was missing from the list of types that were prevented from using the std::formatter partial specialization for integer types. That partial specialization was also matching cv-qualified integer types, because std::integral is t

[committed] libstdc++: Silence -Woverloaded-virtual warning in cxx11-ios_failure.cc

Tested x86_64-linux. Pushed to trunk. -- >8 -- libstdc++-v3/ChangeLog: * src/c++11/cxx11-ios_failure.cc (__iosfail_type_info): Unhide the three-arg overload of __do_upcast. --- libstdc++-v3/src/c++11/cxx11-ios_failure.cc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/libs

[committed] libstdc++: Use constexpr instead of _GLIBCXX20_CONSTEXPR in

Tested x86_64-linux. Pushed to trunk. -- >8 -- For the operator<=> overload we can use the 'constexpr' keyword directly, because we know the language dialect is at least C++20. libstdc++-v3/ChangeLog: * include/bits/stl_vector.h (operator<=>): Use constexpr instead of _GLIBCXX20

[committed] libstdc++: Silence -Wattributes warning in exception_ptr

Tested x86_64-linux. Pushed to trunk. -- >8 -- libstdc++-v3/ChangeLog: * libsupc++/exception_ptr.h (__exception_ptr::_M_safe_bool_dummy): Remove __attribute__((const)) from function returning void. --- libstdc++-v3/libsupc++/exception_ptr.h | 3 +-- 1 file changed, 1 insertion(+

[committed] libstdc++: Fix formatting of most negative chrono::duration [PR116755]

Tested x86_64-linux. Pushed to trunk. -- >8 -- When formatting chrono::duration::min() we were causing undefined behaviour by trying to form the negative of the most negative value. If we convert negative durations with integer rep to the corresponding unsigned integer rep then we can safely repr

[PATCH] config.gcc: Support mips*64*-linux-muslabi64 as ABI64 by default

LLVM introduced this triple support. Let's sync with it. gcc * config.gcc: Add mips*64*-linux-muslabi64 triple support. --- gcc/config.gcc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config.gcc b/gcc/config.gcc index f09ce9f63a0..848fe7da717 100644 --- a/gcc/c

Re: [PATCH v1 1/2] RISC-V: Add testcases for form 3 of signed scalar SAT_ADD

LGTM 於 2024年9月20日 週五 10:19 寫道： > From: Pan Li > > This patch would like to add testcases of the signed scalar SAT_ADD > for form 3. Aka: > > Form 3: > #define DEF_SAT_S_ADD_FMT_3(T, UT, MIN, MAX) \ > T __attribute__((noinline))\ > sat_s_add_##T##_fmt

Re: [PATCH v1 2/2] RISC-V: Add testcases for form 4 of signed scalar SAT_ADD

LGTM 於 2024年9月20日 週五 10:21 寫道： > From: Pan Li > > Form 4: > #define DEF_SAT_S_ADD_FMT_4(T, UT, MIN, MAX) \ > T __attribute__((noinline))\ > sat_s_add_##T##_fmt_4 (T x, T y) \ > {

[committed] libstdc++: Reorder C++26 entries in version.def

Tested x86_64-linux. Pushed to trunk. -- >8 -- This puts the C++26 ftms definitions in alphabetical order. libstdc++-v3/ChangeLog: * include/bits/version.def: Sort C++26 entries alphabetically. * include/bits/version.h: Regenerate. --- libstdc++-v3/include/bits/version.def | 34

Re: [PATCH v2] libstdc++: add default template parameters to algorithms

On Mon, 16 Sept 2024 at 13:53, Giuseppe D'Angelo wrote: > > Hi Jonathan, > > Thank you for picking up (the pieces of) my patch. I've pushed it to trunk now. Thanks for implementing it. > On 15/09/2024 17:00, Jonathan Wakely wrote: > >> Oops, that seems wrong, it seems the correct definition in t

[PATCH v1] Genmatch: Fix ICE for binary phi cfg mismatching [PR116795]

From: Pan Li This patch would like to fix one ICE when try to match the binary phi for below cfg. We check the first edge of the Phi block comes from b0, instead of check the only one edge of b1 comes from the b0 too. Thus, it will result in some code to be recog as .SAT_SUB but it is not, and

[PATCH] [PATCH] Avoid integer overflow in gcc.dg/cpp/charconst-3.c (PR testsuite/116806)

The intermediate expression (unsigned char) '\234' * scale overflows int on int16 targets, causing the test case to fail there. Fixed by performing the arithmetic in unsigned type, as suggested by Andrew Pinski. Regression tested on x86_64-pc-linux-gnu, and on an out-of-tree 16-bit target with si

[PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

From: Mikael Morin Hello, this adds many missing URLs in fortran's lang.opt.url. Surprisingly, the change to fortran's invoke.texi also impacts URL files for rust, m2, ada... I assume it's the expected outcome? Thanks to Jakub for the doc pointers and the analysis help. Checked with make html

Re: [PATCH] doc: Remove @code wrapping of fortran option names [PR116801]

On Sun, Sep 22, 2024 at 04:17:11PM +0200, Mikael Morin wrote: > -@opindex @code{std=}@var{std} option > +@opindex std=@var{std} option IMHO this one should be just @opindex std=@var{std} The option part is superfluous. > -@opindex @code{idirafter @var{dir}} > +@opindex idirafter @var{dir} > -@op

Re: [PATCH v3 08/12] OpenMP: Reject other properties with kind(any)

On 9/21/24 22:52, Jakub Jelinek wrote: On Sat, Sep 21, 2024 at 08:08:29PM -0600, Sandra Loosemore wrote: On 9/20/24 01:41, Jakub Jelinek wrote: + + /* Check for unknown properties. */ if (omp_ts_map[ts_code].valid_properties == NULL) continue; - Why? Why what?