[PATCH][pushed] ada: bump Library_Version to 13.

Pushed as obvious. Martin gcc/ada/ChangeLog: * gnatvsn.ads: Bump Library_Version to 13. --- gcc/ada/gnatvsn.ads | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/ada/gnatvsn.ads b/gcc/ada/gnatvsn.ads index 47a06b96c3c..311a103b2a8 100644 --- a/gcc/ada/gnatvsn.ads

[pushed] c++: traits, array of unknown bound of incomplete

My r161129 changed check_trait_type to reject arrays of unknown bound of incomplete type, but I can't find a rationale for that, and now think it's wrong: the standard just requires that the type be "complete, cv void, or an array of unknown bound." I imagine that allowing arrays of unknown bound

[pushed] c++: typeid and instantiation [PR102651]

PR49387 was a problem with initially asking for a typeid for a class template specialization before it was complete, and later actually filling in the descriptor when the class was complete, and thus disagreeing on the form of the descriptor. I fixed that by forcing the class to be complete, but

Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On Apr 28, 2022, Segher Boessenkool wrote: > On Thu, Apr 28, 2022 at 03:09:54AM -0300, Alexandre Oliva wrote: >> +# ifdef __VSX__ > No space after # (here and everywhere else). 'k, thanks >> + "no __intrinsic_type support for [long] double on PPC w/o >> VSX"); > This change

Re: [PATCH v1] RISC-V: Implement C[LT]Z_DEFINED_VALUE_AT_ZERO

On Thu, 28 Apr 2022 15:11:49 PDT (-0700), philipp.toms...@vrull.eu wrote: Kito, Did you have a chance to take a look at this one? I assume this will have to wait until we reopen for 13... OK for 13? Also: OK for a backport (once a branch for that exists)? I'd assumed it was 13 material when

Re: [PATCH] Disable tests that require fesetround() on platforms without it

On Thu, 28 Apr 2022 15:22:37 PDT (-0700), jos...@codesourcery.com wrote: On Thu, 28 Apr 2022, Palmer Dabbelt wrote: On Thu, 28 Apr 2022 15:12:39 PDT (-0700), jos...@codesourcery.com wrote: > On Thu, 28 Apr 2022, Palmer Dabbelt wrote: > > > +proc check_effective_target_fenv_setround {} { > > +

Re: [PATCH] c++, coroutines: Partial reversion of r12-8308-g15a176a833f23e [PR105426].

On Thu, Apr 28, 2022 at 11:22:45PM +0100, Iain Sandoe wrote: > how about the following, which uniques the names by bind scope, scope nest > and then > sequence within that? That LGTM. > --- a/gcc/cp/coroutines.cc > +++ b/gcc/cp/coroutines.cc > @@ -3913,6 +3913,7 @@ register_local_var_uses (tree

Re: [PATCH] c++, coroutines: Partial reversion of r12-8308-g15a176a833f23e [PR105426].

> On 28 Apr 2022, at 20:26, Jakub Jelinek wrote: > > On Thu, Apr 28, 2022 at 08:17:04PM +0100, Iain Sandoe wrote: >> Signed-off-by: Iain Sandoe >> >> PR c++/105426 >> >> gcc/cp/ChangeLog: >> >> * coroutines.cc (register_local_var_uses): Allow promotion of unnamed >>

Re: [PATCH] Disable tests that require fesetround() on platforms without it

On Thu, 28 Apr 2022, Palmer Dabbelt wrote: > On Thu, 28 Apr 2022 15:12:39 PDT (-0700), jos...@codesourcery.com wrote: > > On Thu, 28 Apr 2022, Palmer Dabbelt wrote: > > > > > +proc check_effective_target_fenv_setround {} { > > > + return [check_runtime fenv_setround { > > > +#include > > >

Re: [PATCH] Disable tests that require fesetround() on platforms without it

On Thu, 28 Apr 2022 15:12:39 PDT (-0700), jos...@codesourcery.com wrote: On Thu, 28 Apr 2022, Palmer Dabbelt wrote: +proc check_effective_target_fenv_setround {} { + return [check_runtime fenv_setround { +#include +#include +int +main (void) +{ + if (fesetround (1)

Re: [PATCH] Disable tests that require fesetround() on platforms without it

On Thu, 28 Apr 2022, Palmer Dabbelt wrote: > +proc check_effective_target_fenv_setround {} { > + return [check_runtime fenv_setround { > +#include > +#include > +int > +main (void) > +{ > + if (fesetround (1) == 0) There is no reason to expect that 1 is a valid

Re: [PATCH v1] RISC-V: Implement C[LT]Z_DEFINED_VALUE_AT_ZERO

Kito, Did you have a chance to take a look at this one? I assume this will have to wait until we reopen for 13... OK for 13? Also: OK for a backport (once a branch for that exists)? Philipp. On Sun, 24 Apr 2022 at 01:44, Philipp Tomsich wrote: > > The Zbb support has introduced ctz and clz

Re: [PATCH] middle-end/105376 - invalid REAL_CST for DFP constant

On Thu, 28 Apr 2022, Richard Biener via Gcc-patches wrote: > We are eventually ICEing in decimal_to_decnumber on non-decimal > REAL_VALUE_TYPE that creep in from uses of build_real (..., dconst*) > for DFP types. The following extends the decimal_to_decnumber > special-casing of dconst* to

[PATCH] libstdc++: Update Solaris baselines for GCC 12.1

The following patch updates the Solaris baselines for GCC 12.1. Tested on i386-pc-solaris2.11 and sparc-sun-solaris2.11 (Solaris 11.3 and 11.4 in each case). The only (expected) difference between the 11.3 and 11.4 versions is --- baseline_symbols.txt.s113s 2022-04-28 10:37:11.464068450 +

Re: [PATCH] c++, coroutines: Partial reversion of r12-8308-g15a176a833f23e [PR105426].

On Thu, Apr 28, 2022 at 08:17:04PM +0100, Iain Sandoe wrote: > Signed-off-by: Iain Sandoe > > PR c++/105426 > > gcc/cp/ChangeLog: > > * coroutines.cc (register_local_var_uses): Allow promotion of unnamed > temporaries to coroutine frame copies. > --- > gcc/cp/coroutines.cc |

Ping #4: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR target/102059

Ping #4: | Date: Tue, 12 Apr 2022 21:14:55 -0400 | From: Michael Meissner | Subject: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR target/102059 | Message-ID: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593153.html -- Michael Meissner, IBM PO Box 98, Ayer,

[PATCH] c++, coroutines: Partial reversion of r12-8308-g15a176a833f23e [PR105426].

The changes to fix PR 105287 included a tightening of the constraints on which variables are promoted to frame copies. This has exposed that we are failing to name some variables that should be promoted. The long-term fix is to address the cases where the naming has been missed, but for the

Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd

> Given that 12 has been branched off, is it OK now to commit this patch? How does the patch affect the results of “make check-gfortran”? How many tests that failed or were unsupported pass? FX

Re: [PATCH] Replace EVRP in DOM with ranger.

On 4/28/2022 10:30 AM, Aldy Hernandez wrote: [Jeff, this is the same patch I sent you last week with minor tweaks to the commit message.] And I just dropped it into the tester.  We should have the vast majority of targets tested by this time tomorrow. [Despite the verbosity of the

[wwwdocs] gcc-12/changes.html: Document the RISC-V libstdc++ -latomic detection

--- IMO this one is worth documenting too, not sure if it's too late for gcc-12's docs (due to those branch commits) so I haven't committed it yet to avoid any fallout. --- htdocs/gcc-12/changes.html | 3 +++ 1 file changed, 3 insertions(+) diff --git a/htdocs/gcc-12/changes.html

[committed] analyzer: handle repeated accesses after init of unknown size [PR105285]

PR analyzer/105285 reports a false positive from -Wanalyzer-null-dereference on git.git's reftable/reader.c. A reduced version of the problem can be seen in test_1a of gcc.dg/analyzer/symbolic-12.c in the following: void test_1a (void *p, unsigned next_off) { struct st_1 *r = p;

[committed] analyzer: add .fpath.txt dumps to -fdump-analyzer-feasibility

I found this extension to -fdump-analyzer-feasibility very helpful when debugging PR analyzer/105285. Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to trunk as r13-6-gd8586b00dd00a1783862da5f0c8811a740400074. gcc/analyzer/ChangeLog: * diagnostic-manager.cc

Re: [committed] Fix more problems with new linker warnings

On Thu, Apr 28, 2022 at 9:59 AM Jeff Law wrote: > > > > On 4/28/2022 10:27 AM, H.J. Lu wrote: > > On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches > > wrote: > >> As I mentioned in the original thread, my change to pr94157_0 was an > >> attempt to avoid these warnings by passing a magic

[PING wwwdocs PATCH v2] document zero-width field ABI changes on MIPS

Ping. On Wed, 2022-04-06 at 23:26 +0800, Xi Ruoyao via Gcc-patches wrote: > Document ABI changes in r12-7961, 7962, and 8023.  Ok for wwwdocs? > > --- >  htdocs/gcc-12/changes.html | 25 - >  1 file changed, 24 insertions(+), 1 deletion(-) > > diff --git

Re: [PATCH] c++: partial ordering and dependent operator expr [PR105425]

On Thu, Apr 28, 2022 at 12:53:06PM -0400, Patrick Palka wrote: > Here ever since r12-6022-gbb2a7f80a98de3 we stopped deeming the partial > specialization #2 to be more specialized than #1 ultimately because > dependent operator expressions now have a DEPENDENT_OPERATOR_TYPE type > instead of an

Re: [patch, fortran, doc] Mention new CONVERT options for POWER

Hi Thomas, On 27 April 2022 22:34:39 CEST, Thomas Koenig via Fortran wrote: +@item @code{'big_endian'} Do all unformatted I/O in big_endian mod.e ISTM that this should be s/mod.e/mode./ ? thanks,

Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd

Given that 12 has been branched off, is it OK now to commit this patch? On 22-04-14 16:09:35, Piotr Kubaj wrote: > On 22-04-14 09:05:17, FX wrote: > > Hi, > > > > > can you check the following patch? > > > > Why restrict it to powerpc-freebsd only, and not all freebsd? Do they > > differ? >

Re: [PATCH] libstdc++: Update documentation about copyright and GPL notices in tests

On Thu, 28 Apr 2022 at 17:45, Koning, Paul via Libstdc++ wrote: > > > > > On Apr 28, 2022, at 8:37 AM, Jonathan Wakely via Gcc-patches > > wrote: > > > > I intend to commit this patch soon. This isn't changing the policy, just > > adjusting the docs to match the current policy. > > > > I'm open

Re: [committed] Fix more problems with new linker warnings

On 4/28/2022 10:27 AM, H.J. Lu wrote: On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches wrote: As I mentioned in the original thread, my change to pr94157_0 was an attempt to avoid these warnings by passing a magic flag to the linker. Of course we may not be using GNU ld. Or we may

[PATCH] c++: partial ordering and dependent operator expr [PR105425]

Here ever since r12-6022-gbb2a7f80a98de3 we stopped deeming the partial specialization #2 to be more specialized than #1 ultimately because dependent operator expressions now have a DEPENDENT_OPERATOR_TYPE type instead of an empty type, and this made unify stop deducing T(2) == 1 for K during

Re: [PATCH] libstdc++: Update documentation about copyright and GPL notices in tests

> On Apr 28, 2022, at 8:37 AM, Jonathan Wakely via Gcc-patches > wrote: > > I intend to commit this patch soon. This isn't changing the policy, just > adjusting the docs to match the current policy. > > I'm open to suggestions for better ways to phrase the second sentence, > clarifying that

[patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12

Hi, the attached patch documents the support for IEEE long double for Fortran. OK? Suggestions for better wording? Best regards Thomas Mention support for IEEE 128-bit long double for Fortran. * htdocs/gcc-12/changes.html: Mention support for IEEE 128-bit long

[PATCH] Replace EVRP in DOM with ranger.

[Jeff, this is the same patch I sent you last week with minor tweaks to the commit message.] [Despite the verbosity of the message, this is actually a pretty straightforward patch. It should've gone in last cycle, but there was a nagging regression I couldn't get to until after stage1 had

Re: [committed] Fix more problems with new linker warnings

On Thu, Apr 28, 2022 at 9:10 AM Jeff Law via Gcc-patches wrote: > > As I mentioned in the original thread, my change to pr94157_0 was an > attempt to avoid these warnings by passing a magic flag to the linker. > Of course we may not be using GNU ld. Or we may be on a non-elf target > where the

[committed] Fix more problems with new linker warnings

As I mentioned in the original thread, my change to pr94157_0 was an attempt to avoid these warnings by passing a magic flag to the linker.  Of course we may not be using GNU ld.  Or we may be on a non-elf target where the flag I used doesn't exist.  Or we may even be on a ELF target where

Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On Thu, Apr 28, 2022 at 03:56:18PM +0200, Matthias Kretz wrote: > On Thursday, 28 April 2022 08:09:54 CEST Alexandre Oliva via Gcc-patches > wrote: > > libstdc++'s bits/simd.h section for PPC (Altivec) defines various > > intrinsic vector types that are only available along with VSX: 64-bit > >

[PATCH] Disable tests that require fesetround() on platforms without it

Some tests check for fenv and then proceed to use fesetround() directly, but some platforms (at least RISC-V soft-float) have fenv but don't support rounding modes. This adds a DG check that fesetround() actually functions, which is then used by all the tests that call fesetround() explicitly.

Re: [PATCH] doc: Remove misleading text about multilibs for IEEE long double

On Thu, Apr 28, 2022 at 10:46:17AM +0100, Jonathan Wakely wrote: > IIUC this text is not true (maybe it was back in 2018?) Initially I thought the way to transition to IEEE 128-bit long double would be through multilibs, but we never installed multilibs for the different long double types. So

Re: [PATCH] tree-optimization/105219 - bogus max iters for vectorized epilogue

On 27/04/2022 15:03, Richard Biener wrote: On Wed, 27 Apr 2022, Richard Biener wrote: The following makes sure to take into account prologue peeling when trying to narrow down the maximum number of iterations computed for the epilogue of a vectorized epilogue. Bootstrap & regtest running on

Re: [PATCH v2] c++: ICE with temporary of class type in DMI [PR100252]

On Thu, Apr 28, 2022 at 10:12:04AM -0400, Patrick Palka wrote: > On Wed, 27 Apr 2022, Marek Polacek wrote: > > > On Wed, Apr 27, 2022 at 11:00:46AM -0400, Patrick Palka wrote: > > > On Tue, 26 Apr 2022, Marek Polacek wrote: > > > > > > > Consider > > > > > > > > struct A { > > > > int x;

Re: libgomp GCN plugin: Clean up unused references to system-provided HSA Runtime library (was: [PATCH 1/4] Remove build dependence on HSA run-time)

On 06/04/2022 11:02, Thomas Schwinge wrote: Hi! On 2021-01-14T15:50:23+0100, I wrote: I'm raising here an issue with HSA libgomp plugin code changes from a while ago. While HSA is now no longer relevant for GCC master branch, the same code has also been copied into the GCN libgomp plugin.

Re: [PATCH v2] c++: ICE with temporary of class type in DMI [PR100252]

On Wed, 27 Apr 2022, Marek Polacek wrote: > On Wed, Apr 27, 2022 at 11:00:46AM -0400, Patrick Palka wrote: > > On Tue, 26 Apr 2022, Marek Polacek wrote: > > > > > Consider > > > > > > struct A { > > > int x; > > > int y = x; > > > }; > > > > > > struct B { > > > int x = 0; >

Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics

On Thursday, 28 April 2022 08:09:54 CEST Alexandre Oliva via Gcc-patches wrote: > libstdc++'s bits/simd.h section for PPC (Altivec) defines various > intrinsic vector types that are only available along with VSX: 64-bit > long double, double, (un)signed long long, and 64-bit (un)signed long. Oh,

[PING] libgomp GCN plugin: Clean up unused references to system-provided HSA Runtime library (was: [PATCH 1/4] Remove build dependence on HSA run-time)

Hi! Ping. On 2022-04-06T12:02:08+0200, I wrote: > On 2021-01-14T15:50:23+0100, I wrote: >> I'm raising here an issue with HSA libgomp plugin code changes from a >> while ago. While HSA is now no longer relevant for GCC master branch, >> the same code has also been copied into the GCN libgomp

[PING] libgomp testsuite: Don't amend 'LD_LIBRARY_PATH' for system-provided HSA Runtime library (was: [PATCH 1/4] Remove build dependence on HSA run-time)

Hi! Ping. On 2022-04-06T11:20:47+0200, I wrote: > On 2021-01-14T15:50:23+0100, I wrote: >> I'm raising here an issue with HSA libgomp plugin code changes from a >> while ago. While HSA is now no longer relevant for GCC master branch, >> the same code has also been copied into the GCN libgomp

Re: libgomp nvptx plugin: Split 'PLUGIN_NVPTX_DYNAMIC' into 'PLUGIN_NVPTX_INCLUDE_SYSTEM_CUDA_H' and 'PLUGIN_NVPTX_LINK_LIBCUDA'

Hi Tom! On 2022-04-08T09:35:44+0200, Tom de Vries wrote: > On 4/8/22 00:27, Thomas Schwinge wrote: >> On 2017-01-13T19:11:23+0100, Jakub Jelinek wrote: >>> Especially for distributions it is undesirable to need to have proprietary >>> CUDA libraries and headers installed when building GCC. >>

Re: Patch ping Re: [PATCH] i386: Fix up ix86_gimplify_va_arg [PR105331]

On 4/28/2022 4:31 AM, Richard Biener wrote: On Thu, 28 Apr 2022, Jakub Jelinek wrote: On Thu, Apr 28, 2022 at 10:39:39AM +0200, Uros Bizjak wrote: Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2022-04-22 Jakub Jelinek PR target/105331 *

Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics

Hi! On Thu, Apr 28, 2022 at 03:09:54AM -0300, Alexandre Oliva wrote: > libstdc++'s bits/simd.h section for PPC (Altivec) defines various > intrinsic vector types that are only available along with VSX: 64-bit > long double, double, (un)signed long long, and 64-bit (un)signed long. > >

[pushed] testsuite,X86: Fix missing USER_LABEL_PREFIX cases.

Yet another set of testcases that do not account for targets that use __USER_LABEL_PREFIX__. tested on x86_64 Linux and Darwin, pushed to master, thanks, Iain Signed-off-by: Iain Sandoe gcc/testsuite/ChangeLog: * gcc.target/i386/memcpy-strategy-10.c: Account for

[pushed] testsuite: Add target requires for ifuncs to mv31.C.

g++.target/i386/mv31.C fails on targets without ifuncs support so add the necessary target supports guard. tested on x86_64 linux and darwin. pushed to master, thanks, Iain Signed-off-by: Iain Sandoe gcc/testsuite/ChangeLog: * g++.target/i386/mv31.C: Add target supports guard for

[PATCH] libstdc++: Update documentation about copyright and GPL notices in tests

I intend to commit this patch soon. This isn't changing the policy, just adjusting the docs to match the current policy. I'm open to suggestions for better ways to phrase the second sentence, clarifying that our tests generally have nothing novel or "authored". -- >8 -- There is no need to

[committed] libstdc++: Fix error reporting in filesystem::copy [PR99290]

Tested x86_64-linux, pushed to trunk. I'll backport this too. -- >8 -- The recursive calls to filesystem::copy should stop if any of them reports an error. libstdc++-v3/ChangeLog: PR libstdc++/99290 * src/c++17/fs_ops.cc (fs::copy): Pass error_code to directory_iterator

Re: [PATCH] Honor COMDAT for mergeable constant sections

On Thu, 2022-04-28 at 13:27 +0200, Jakub Jelinek wrote: > On Thu, Apr 28, 2022 at 01:03:26PM +0200, Ilya Leoshkevich wrote: > > This is determined by default_elf_select_rtx_section ().  If we > > don't > > want to mix non-reloc and reloc constants, we need to define a > > special > > section

Re: [PATCH] cgraph: Don't verify semantic_interposition flag for aliases [PR105399]

> On Thu, Apr 28, 2022 at 01:54:51PM +0200, Jan Hubicka wrote: > > > --- gcc/cgraph.cc.jj 2022-04-20 09:24:12.194579146 +0200 > > > +++ gcc/cgraph.cc 2022-04-27 11:53:52.102173154 +0200 > > > @@ -3488,7 +3488,9 @@ cgraph_node::verify_node (void) > > >"returns a pointer"); > > >

Re: [PATCH] cgraph: Don't verify semantic_interposition flag for aliases [PR105399]

On Thu, Apr 28, 2022 at 01:54:51PM +0200, Jan Hubicka wrote: > > --- gcc/cgraph.cc.jj2022-04-20 09:24:12.194579146 +0200 > > +++ gcc/cgraph.cc 2022-04-27 11:53:52.102173154 +0200 > > @@ -3488,7 +3488,9 @@ cgraph_node::verify_node (void) > > "returns a pointer"); > >

Re: [PATCH] cgraph: Don't verify semantic_interposition flag for aliases [PR105399]

Hello, > Hi! > > The following testcase ICEs, because the ctors during cc1plus all have > !opt_for_fn (decl, flag_semantic_interposition) - they have NULL > DECL_FUNCTION_SPECIFIC_OPTIMIZATION (decl) and optimization_default_node > is for -Ofast and so has flag_semantic_interposition cleared. >

Re: [PATCH] c++, coroutines: Avoid expanding within templates [PR103868]

On 4/28/22 04:24, Iain Sandoe wrote: Hi Jason, On 20 Apr 2022, at 04:45, Jason Merrill wrote: On 4/18/22 15:49, Eric Gallager via Gcc-patches wrote: On Mon, Apr 18, 2022 at 10:01 AM Iain Sandoe via Gcc-patches wrote: From: Nathan Sidwell This is a forward-port of a patch by Nathan

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

On 4/28/22 04:28, Iain Sandoe wrote: Hi Jason, On 20 Apr 2022, at 03:14, Jason Merrill wrote: On 4/18/22 10:02, Iain Sandoe wrote: 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

Re: [PATCH] ipa: Release body of clone_of when removing its last clone (PR 100413)

> Hi, > > In the PR, the verifier complains that we did not manage to remove the > body of a node and it is right. The node is kept for materialization > of two clones but after one is materialized, the other one is removed > as unneeded (as a part of delete_unreachable_blocks_update_callgraph).

Re: [PATCH] Honor COMDAT for mergeable constant sections

On Thu, Apr 28, 2022 at 01:03:26PM +0200, Ilya Leoshkevich wrote: > This is determined by default_elf_select_rtx_section (). If we don't > want to mix non-reloc and reloc constants, we need to define a special > section there. > > It seems to me, however, that this all would be made purely for

[committed] d: Merge upstream dmd 313d28b3d, druntime e361d200.

Hi, This patches merges the D front-end with upstream dmd 313d28b3d, and the D runtime library with upstream druntime e361d200. D front-end changes: - Import latest bug fixes from the 2.100 release branch. - Fix signatures of extern C++ functions that have size_t parameters.

Re: [PATCH] Honor COMDAT for mergeable constant sections

On Wed, 2022-04-27 at 14:46 +0200, Jakub Jelinek wrote: > On Wed, Apr 27, 2022 at 02:23:00PM +0200, Jakub Jelinek wrote: > > On Wed, Apr 27, 2022 at 11:59:49AM +0200, Ilya Leoshkevich wrote: > > > I get a .LASANPC reloc there in the first place because of > > >

Re: Patch ping Re: [PATCH] i386: Fix up ix86_gimplify_va_arg [PR105331]

On Thu, 28 Apr 2022, Jakub Jelinek wrote: > On Thu, Apr 28, 2022 at 10:39:39AM +0200, Uros Bizjak wrote: > > > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > > > > > > > 2022-04-22 Jakub Jelinek > > > > > > > > PR target/105331 > > > > *

Re: Patch ping Re: [PATCH] i386: Fix up ix86_gimplify_va_arg [PR105331]

On Thu, Apr 28, 2022 at 10:39:39AM +0200, Uros Bizjak wrote: > > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? > > > > > > 2022-04-22 Jakub Jelinek > > > > > > PR target/105331 > > > * config/i386/i386.cc (ix86_gimplify_va_arg): Mark va_arg_tmp > > >

Re: [PATCH] doc: Remove misleading text about multilibs for IEEE long double

On Thu, Apr 28, 2022 at 10:46:17AM +0100, Jonathan Wakely via Gcc-patches wrote: > IIUC this text is not true (maybe it was back in 2018?) > > OK for trunk? > > Which branches should it be on too, all of them? > > -- >8 -- > > The choice of ieee or ibm long double format is orthogonal to

[PATCH 12/12] arm: implement bti injection

Hi all, this patch enables Branch Target Identification Armv8.1-M Mechanism [1]. This is achieved by using the bti pass made common with Aarch64. The pass iterates through the instructions and adds the necessary BTI instructions at the beginning of every function and at every landing pads

[PATCH 11/12] aarch64: Make bti pass generic so it can be used by the arm backend

Hi all, this patch splits and restructures the aarch64 bti pass code in order to have it usable by the arm backend as well. These changes have no functional impact. Best Regards Andrea gcc/Changelog * config.gcc (aarch64*-*-*): Rename 'aarch64-bti-insert.o' into

[PATCH 10/12] arm: Implement cortex-M return signing address codegen

Hi all, this patch enables address return signature and verification based on Armv8.1-M Pointer Authentication [1]. To sign the return address, we use the PAC R12, LR, SP instruction upon function entry. This is signing LR using SP and storing the result in R12. R12 will be pushed into the

[PATCH 9/12] arm: Make libgcc bti compatible

This change add bti instructions at the beginning of arm specific libgcc hand written assembly routines. 2022-03-31 Andrea Corallo * libgcc/config/arm/crti.S (FUNC_START): Add bti instruction if necessary. * libgcc/config/arm/lib1funcs.S (THUMB_FUNC_START, FUNC_START):

[PATCH 8/12] arm: Introduce multilibs for PACBTI target feature

This patch add the following new multilibs. thumb/v8.1-m.main+pacbti/mbranch-protection/nofp thumb/v8.1-m.main+pacbti+dp/mbranch-protection/soft thumb/v8.1-m.main+pacbti+dp/mbranch-protection/hard thumb/v8.1-m.main+pacbti+fp/mbranch-protection/soft

[PATCH] doc: Remove misleading text about multilibs for IEEE long double

IIUC this text is not true (maybe it was back in 2018?) OK for trunk? Which branches should it be on too, all of them? -- >8 -- The choice of ieee or ibm long double format is orthogonal to multilibs, as the two sets of symbols co-exist and don't need a separate multilib. gcc/ChangeLog:

[PATCH 7/12] arm: Emit build attributes for PACBTI target feature

This patch emits assembler directives for PACBTI build attributes as defined by the ABI. gcc/ChangeLog: * config/arm/arm.c (arm_file_start): Emit EABI attributes for Tag_PAC_extension,

[PATCH 6/12] arm: Add pointer authentication for stack-unwinding runtime

This patch adds authentication for when the stack is unwound when an exception is taken. All the changes here are done to the runtime code in libgcc's unwinder code for Arm target. All the changes are guarded under defined (__ARM_FEATURE_PAC_DEFAULT) and activated only if the +pacbti feature is

[PATCH 5/12] arm: Implement target feature macros for PACBTI

This patch implements target feature macros when PACBTI is enabled through the -march option or -mbranch-protection. The target feature macros __ARM_FEATURE_PAC_DEFAULT and __ARM_FEATURE_BTI_DEFAULT are specified in ARM ACLE

[PATCH 4/12] arm: Add testsuite library support for PACBTI target

Add targeting-checking entities for PACBTI in testsuite framework. Pre-approved with the requested changes here . gcc/testsuite/ChangeLog: * testsuite/lib/target-supports.exp:

[PATCH 3/12] arm: Add option -mbranch-protection

[PATCH 3/12] arm: Add option -mbranch-protection Add -mbranch-protection option. This option enables the code-generation of pointer signing and authentication instructions in function prologues and epilogues. gcc/ChangeLog: * config/arm/arm.c (arm_configure_build_target): Parse and

[PATCH 2/12] arm: Add Armv8.1-M Mainline target feature +pacbti

This patch adds the -march feature +pacbti to Armv8.1-M Mainline. This feature enables pointer signing and authentication instructions on M-class architectures. Pre-approved here . gcc/Changelog: * config/arm/arm.h

Re: [PATCH]middle-end testsuite: Backport testsuite changes from GCC 12 to GCC 11

On Thu, 28 Apr 2022, Tamar Christina wrote: > Hi All, > > This backports the testsuite changes from mainline to GCC 11. > This enables some tests that were not running and fix some > unresolved cases. The test output are adjusted to what GCC 11 could detect. > > Regtested on

Re: [PATCH][_GLIBCXX_INLINE_VERSION] Fix std::random_device definition

On Thu, 28 Apr 2022 at 05:56, François Dumont via Libstdc++ wrote: > > Hi > > Still time for this fix for gcc 12 ? What needs fixing? std::random_device is already declared in the versioned namespace in : namespace std _GLIBCXX_VISIBILITY(default) { _GLIBCXX_BEGIN_NAMESPACE_VERSION ...

[PATCH] ipa: Release body of clone_of when removing its last clone (PR 100413)

Hi, In the PR, the verifier complains that we did not manage to remove the body of a node and it is right. The node is kept for materialization of two clones but after one is materialized, the other one is removed as unneeded (as a part of delete_unreachable_blocks_update_callgraph). The problem

[PATCH]middle-end testsuite: Backport testsuite changes from GCC 12 to GCC 11

Hi All, This backports the testsuite changes from mainline to GCC 11. This enables some tests that were not running and fix some unresolved cases. The test output are adjusted to what GCC 11 could detect. Regtested on aarch64-none-linux-gnu and no issues. Ok for GCC 11? Thanks, Tamar

[PATCH 1/12] arm: Make mbranch-protection opts parsing common to AArch32/64

Hi all, This change refactors all the mbranch-protection option parsing code and types to make it common to both AArch32 and AArch64 backends. This change also pulls in some supporting types from AArch64 to make it common (aarch_parse_opt_result). The significant changes in this patch are the

[PATCH 0/12] arm: Enables return address verification and branch target identification on Cortex-M

Hi all, this series enables return address verification and branch target identification based on Armv8.1-M Pointer Authentication and Branch Target Identification Extension [1] for Arm Cortex-M. This feature is controlled by the newly introduced '-mbranch-protection' option, contextually the

Re: Patch ping Re: [PATCH] i386: Fix up ix86_gimplify_va_arg [PR105331]

On Thu, Apr 28, 2022 at 10:31 AM Jakub Jelinek wrote: > > Hi! > > I'd like to ping this patch. I know it isn't a full week yet, but we are > almost out of P1s and GCC 12 branching is any time now. > > Thanks: > On Fri, Apr 22, 2022 at 09:25:04AM +0200, Jakub Jelinek via Gcc-patches wrote: > > On

Patch ping Re: [PATCH] i386: Fix up ix86_gimplify_va_arg [PR105331]

Hi! I'd like to ping this patch. I know it isn't a full week yet, but we are almost out of P1s and GCC 12 branching is any time now. Thanks: On Fri, Apr 22, 2022 at 09:25:04AM +0200, Jakub Jelinek via Gcc-patches wrote: > On the following testcase we emit a bogus > 'va_arg_tmp.5' may be used

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

Hi Jason, > On 20 Apr 2022, at 03:14, Jason Merrill wrote: > > On 4/18/22 10:02, Iain Sandoe wrote: >> 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

Re: [PATCH] c++, coroutines: Avoid expanding within templates [PR103868]

Hi Jason, > On 20 Apr 2022, at 04:45, Jason Merrill wrote: > > On 4/18/22 15:49, Eric Gallager via Gcc-patches wrote: >> On Mon, Apr 18, 2022 at 10:01 AM Iain Sandoe via Gcc-patches >> wrote: >>> >>> From: Nathan Sidwell >>> >>> This is a forward-port of a patch by Nathan (against 10.x)

Re: [PATCH] cgraph: Don't verify semantic_interposition flag for aliases [PR105399]

On Thu, 28 Apr 2022, Jakub Jelinek wrote: > Hi! > > The following testcase ICEs, because the ctors during cc1plus all have > !opt_for_fn (decl, flag_semantic_interposition) - they have NULL > DECL_FUNCTION_SPECIFIC_OPTIMIZATION (decl) and optimization_default_node > is for -Ofast and so has

Re: [PATCH] testsuite: vect: update unaligned message

On Thu, 28 Apr 2022, Alexandre Oliva wrote: > > gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c covers ppc variants > that accept and reject misaligned accesses. The message that it > expects for rejection was removed in the gcc-11 development cycle by > commit r11-1969. The patch adjusted

Re: [patch, fortran, doc] Mention new CONVERT options for POWER

On Wed, Apr 27, 2022 at 10:34 PM Thomas Koenig via Fortran wrote: > > Hi, > > as we say in German "Nicht documentiert ist nicht gemacht", if > it is not documented, it wasn't done. > > So I thought it would be time to document the changes to the various > ways of specifying CONVERT before gcc12

Re: Unreviewed D doc patch

On Wed, Apr 27, 2022 at 6:27 PM Rainer Orth wrote: > > The following patch > > doc: Document Solaris D bootstrap requirements [PR 103528] > https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591844.html > > has remained unreviewed for 6 weeks now, despite a reminder. It would

[PATCH] middle-end/105376 - invalid REAL_CST for DFP constant

We are eventually ICEing in decimal_to_decnumber on non-decimal REAL_VALUE_TYPE that creep in from uses of build_real (..., dconst*) for DFP types. The following extends the decimal_to_decnumber special-casing of dconst* to build_real, avoiding the bogus REAL_CSTs from creeping into the IL and

[PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics

libstdc++'s bits/simd.h section for PPC (Altivec) defines various intrinsic vector types that are only available along with VSX: 64-bit long double, double, (un)signed long long, and 64-bit (un)signed long. experimental/simd/standard_abi_usable{,_2}.cc tests error out reporting the unmet

[PATCH][stage1] Embed real_value into REAL_CST

The following removes the indirection to real_value from REAL_CST which doesn't seem to serve any useful purpose. Any sharing can be achieved by sharing the actual REAL_CST (which is what usually happens when copying trees) and sharing of real_value amongst different REAL_CST doesn't happen as

[PATCH] testsuite: vect: update unaligned message

gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c covers ppc variants that accept and reject misaligned accesses. The message that it expects for rejection was removed in the gcc-11 development cycle by commit r11-1969. The patch adjusted multiple tests to use the message introduced in r11-1945,