[PATCH 2/2] Remove dead vect_recog_mixed_size_cond_pattern

vect_recog_mixed_size_cond_pattern only applies to COMPARISON_CLASS_P rhs1 COND_EXPRs which no longer appear - the following removes it. Its testcases still pass, I believe the situation is mitigated by bool pattern handling of the compare use in COND_EXPRs. Boostrap and regtest running on x86_64-

[PATCH] Testing: remove dead code in adjust_bool_pattern

I believe the comparison handling in adjust_bool_pattern is dead after no longer queueing them but there's a do_compare goto that's not obviously dead. So I'm looking for testcases - the code path would build a COND_EXPR with a comparison embedded. Bootstrap and regtest running on x86_64-unknown-

[PATCH 1/2] Remove dead code in vectorizer pattern recog

The following removes the code path in vect_recog_mask_conversion_pattern dealing with comparisons in COND_EXPRs. That can no longer happen. Bootstrap and regtest running on x86_64-unknown-linux-gnu. * tree-vect-patterns.cc (vect_recog_mask_conversion_pattern): Remove COMPARISON_

[PATCH] Remove code in vectorizer pattern recog relying on vec_cond{u,eq,}

With the intent to rely on vec_cond_mask and vec_cmp patterns comparisons do not need rewriting into COND_EXPRs that eventually combine to vec_cond{u,eq,}. Bootstrap and regtest running on x86_64-unknown-linux-gnu. * tree-vect-patterns.cc (check_bool_pattern): For comparisons we d

[Ada] Fix PR ada/62122

This is an old glitch in the GNAT RM. Tested on x86-64/Linux, applied on the mainline. 2024-10-26 Eric Botcazou PR ada/62122 * doc/gnat_rm/implementation_defined_attributes.rst (Unrestricted_Access): Remove null exclusion. * gnat_rm.texi: Regenerate. -- Eric

Re: [PATCH] doc/cpp: Document __has_include_next

Hi! Arsen Arsenović writes: > OK for trunk? Seems to build and render fine with makeinfo --info and > --html. Typesetting it, I see overfull and underfull hboxes, but I > suspect these were here for a while.. Gentle ping on this patch. TIA, have a lovely day. -- Arsen Arsenović signature.

[PATCH 0/2] RISC-V:Add Cache Management Operation ISA Extensions Intrinsics

From: yulong This patchset adds intrinsic support for CMOs extensions.But it not include prefetchi. cf. ; Patch 1: Add Zicbom/z/p intrinsic support Patch 2: Add test cases. yulong (2): Add intrinsic support for the CMOs extensions

[PATCH 2/2] Add intrinsic cases for the CMOs extensions

From: yulong gcc/testsuite/ChangeLog: * gcc.target/riscv/cmo-32.c: New test. * gcc.target/riscv/cmo-64.c: New test. --- gcc/testsuite/gcc.target/riscv/cmo-32.c | 52 + gcc/testsuite/gcc.target/riscv/cmo-64.c | 52 + 2 files change

[PATCH 1/2] Add intrinsic support for the CMOs extensions

From: yulong gcc/ChangeLog: * config.gcc: Add riscv_cmo.h. * config/riscv/riscv_cmo.h: New file. --- gcc/config.gcc | 2 +- gcc/config/riscv/riscv_cmo.h | 84 2 files changed, 85 insertions(+), 1 deletion(-) create mode 10064

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

> On 26 Oct 2024, at 22:41, Thomas Koenig wrote: > > Am 26.10.24 um 22:10 schrieb Iain Sandoe: >>> Pushed (4727bfb37701f3fef98a5f8b60dcd2daa82e8143). >> This seems to have broken —enable-languages=all bootstrap with >> /src-local/gcc-master/gcc/fortran/intrinsic.texi:39: node `Intrinsic >> P

[PATCH] guality tests: Silence gdb debuginfod warning

When gdb defaults to use debuginfod, gdb warns guality tests: Spawning: gdb -nx -nw -quiet -batch -x pr36728-2.gdb ./pr36728-2.exe spawn gdb -nx -nw -quiet -batch -x pr36728-2.gdb ./pr36728-2.exe Breakpoint 1 at 0x4004ba: file /export/gnu/import/git/gitlab/x86-gcc/gcc/testsui te/gcc.dg/guality/pr3

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

Am 26.10.24 um 22:10 schrieb Iain Sandoe: Pushed (4727bfb37701f3fef98a5f8b60dcd2daa82e8143). This seems to have broken —enable-languages=all bootstrap with /src-local/gcc-master/gcc/fortran/intrinsic.texi:39: node `Intrinsic Procedures' lacks menu item for `UINT' despite being its Up target

[pushed] doc, fortran: Add a missing menu item.

Tested on x86_64-darwin21 and linux, with makeinfo 6.7 pushed to trunk, thanks Iain --- 8< --- The changes in r15-4697-g4727bfb37701 omit a menu entry which causes a bootstrap fail when Fortran is included for at least makeinfo 6.7. Fixed thus. gcc/fortran/ChangeLog: * intrinsic.texi: A

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

On Sat, Oct 26, 2024 at 05:16:54PM +0200, Thomas Koenig wrote: > > OK for trunk? > OK, but see below. > +@item @code{SUM}, @pxref{SUM} > +@item @code{TRANSPOSE}, @pxref{TRANSPOSE} > +@item @code{TRANSFER}, @pxref{TRANSFER} > @end itemize > + > +The following intrincis are enabled with @option{

[patch, Fortran, doc] Update descriptions for UNSIGNED

Hello world, the attached patch adds documentation for the long list of intrinsics which take UNSIGNED arguments. Checked with "make html", "make pdf" and "make info". gcc/fortran/ChangeLog: * gfortran.texi: Correct reference to make clear that UNSIGNED will not be part of F202Y

RE: [PATCH] i386: Add _MM_FROUND_TO_NEAREST_TIES_EVEN to smmintrin.h

This patch adds the standard macro definition _MM_FROUND_TO_NEAREST_TIES_EVEN for specifying the IEEE rounding to nearest attribute `roundTiesToEven` for AVX512 floating-point intrinsics. More information can be found in the original email to this list https://gcc.gnu.org/pipermail/gcc-patc

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

Hi Thomas > On 26 Oct 2024, at 18:28, Thomas Koenig wrote: > > Hi Steve, > >>> OK for trunk? >>> >> OK, but see below. > > Pushed (4727bfb37701f3fef98a5f8b60dcd2daa82e8143). This seems to have broken —enable-languages=all bootstrap with /src-local/gcc-master/gcc/fortran/intrinsic.texi:39:

Re: [PATCH] Add 'cobol' to Makefile.def, take 2

On Sat, 26 Oct 2024 11:22:20 +0800 Xi Ruoyao wrote: > The changelog is not formatted correctly. gcc/ has its own > changelog. And gcc/cobol should have its own changelog too, like all > other frontends. Thank you for pointing that out. I now have [snip] Subject: [PATCH] Add 'cobol' to 10 fil

[PATCH] c: detect variably-modified types [PR117145,PR117245,PR100420]

Here is a patch that hopefully fixes the last cases where we do not tag variably-modified types correctly. It is probably best to look at the c-typeck.cc changes first. Martin c: detect variably-modified types [PR117145,PR117245,PR100420] This fixes two cases where variably-modif

Re: [PATCH] tree: Mark PAREN_EXPR and VEC_DUPLICATE_EXPR as non-trapping [PR117234]

> Am 26.10.2024 um 19:06 schrieb Andrew Pinski : > > While looking to fix a possible trapping issue in PHI-OPT's factor, > I noticed that some tree codes could be marked as trapping even > though they don't have a possibility to trap. In the case of PAREN_EXPR, > it is basically a nop except w

Re: [patch, Fortran, doc] Update descriptions for UNSIGNED

Hi Steve, OK for trunk? OK, but see below. Pushed (4727bfb37701f3fef98a5f8b60dcd2daa82e8143). Thanks for the proof-reading! Best regards Thomas

[PATCH] [aarch64] Fix function multiversioning dispatcher link error with LTO

We forgot to apply DECL_EXTERNAL to __init_cpu_features_resolver decl. When building with LTO, the linker cannot find the __init_cpu_features_resolver.lto_priv* symbol, causing the link error. This patch get this fixed by adding DECL_EXTERNAL to the decl. Minimal steps to reproduce the bug: echo

Re: [PATCH v3 10/11] RISC-V: Implement TARGET_GENERATE_VERSION_DISPATCHER_BODY and TARGET_GET_FUNCTION_VERSIONS_DISPATCHER

On 2024/10/24 15:13, Yangyu Chen wrote: This patch implements the TARGET_GENERATE_VERSION_DISPATCHER_BODY and TARGET_GET_FUNCTION_VERSIONS_DISPATCHER for RISC-V. This is used to generate the dispatcher function and get the dispatcher function for function multiversioning. This patch copies ma

Re: [PATCH v7] Target-independent store forwarding avoidance.

On 10/23/24 8:27 AM, Konstantinos Eleftheriou wrote: From: kelefth This pass detects cases of expensive store forwarding and tries to avoid them by reordering the stores and using suitable bit insertion sequences. For example it can transform this: strbw2, [x1, 1] ldr x0

[PATCH] tree: Mark PAREN_EXPR and VEC_DUPLICATE_EXPR as non-trapping [PR117234]

While looking to fix a possible trapping issue in PHI-OPT's factor, I noticed that some tree codes could be marked as trapping even though they don't have a possibility to trap. In the case of PAREN_EXPR, it is basically a nop except when it comes to association across it so it can't trap. In the c

Re: [COMMITTED 4/4] - Implement pointer_or_operator.

Hello, Le 24/10/2024 à 14:53, Andrew MacLeod a écrit : diff --git a/gcc/range-op-ptr.cc b/gcc/range-op-ptr.cc index dd312a80366..ef2b2cce516 100644 --- a/gcc/range-op-ptr.cc +++ b/gcc/range-op-ptr.cc (...) -void -pointer_or_operator::wi_fold (irange &r, tree type, -