Re: [PATCH, rs6000] Change insn condition from TARGET_64BIT to TARGET_POWERPC64 for VSX scalar extract/insert instructions

Hi Haochen, on 2022/8/19 10:35, HAO CHEN GUI wrote: > Hi, > > This patch is for internal issue1136. It changes insn condition from > TARGET_64BIT to TARGET_POWERPC64 for VSX scalar extract/insert instructions. > These instructions all use DI registers and can be invoked with -mpowerpc64 > in a

Re: [PATCH v3] rs6000: Rework ELFv2 support for -fpatchable-function-entry* [PR99888]

Hi Segher, Thanks for the review! on 2022/8/19 01:34, Segher Boessenkool wrote: > Hi! > > On Thu, Aug 18, 2022 at 10:12:48AM +0800, Kewen.Lin wrote: >> As PR99888 and its related show, the current support for >> -fpatchable-function-entry on powerpc ELFv2 doesn't work >> well with global entry

[PATCH, rs6000] Change insn condition from TARGET_64BIT to TARGET_POWERPC64 for VSX scalar extract/insert instructions

Hi, This patch is for internal issue1136. It changes insn condition from TARGET_64BIT to TARGET_POWERPC64 for VSX scalar extract/insert instructions. These instructions all use DI registers and can be invoked with -mpowerpc64 in a 32-bit environment. This patch also changes prototypes of

[wwwdocs] [GCC13] Mention Intel __bf16 support.

Hi The patch is for mention Intel __bf16 support in gcc13. Ok for master ? Thanks, Lingling htdocs/gcc-13/changes.html | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 57bd8724..7d98329c 100644 ---

[PATCH v2] LoongArch: Add support code model extreme.

v1 -> v2: - Modify some description information. - Add options -W[no]extreme-plt, warn about code model extreme not support plt mode, and then disable plt. --- Use five instructions to calculate a signed 64-bit offset relative to the pc. gcc/ChangeLog:

Re: [PING][PATCH] Add instruction level discriminator support.

On 8/3/22 17:25, Eugene Rozenfeld wrote: One more ping for this patch https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596065.html CC Jason since this changes discriminators emitted in dwarf. Thanks, Eugene -Original Message- From: Eugene Rozenfeld Sent: Monday, June 27, 2022

Re: [PATCH] libcpp, v2: Implement C++23 P2290R3 - Delimited escape sequences [PR106645]

On 8/18/22 01:17, Jakub Jelinek wrote: On Wed, Aug 17, 2022 at 10:22:03PM -0400, Jason Merrill wrote: OK, a comment mentioning this should be sufficient. Here is an updated patch with those changes in. So far successfully tested with GXX_TESTSUITE_STDS=98,11,14,17,20,2b make -j32 -k check-gcc

Re: [PATCH v2] c++: Implement -Wself-move warning [PR81159]

On 8/18/22 13:19, Marek Polacek wrote: On Mon, Aug 15, 2022 at 03:54:05PM -0400, Jason Merrill wrote: On 8/9/22 09:37, Marek Polacek wrote: + /* We're looking for *std::move ((T &) ), or + *std::move ((T &) (T *) r) if the argument it a reference. */ + if (!REFERENCE_REF_P (rhs) +

[committed] preprocessor: Support #warning for standard C2x

ISO C2x standardizes the existing #warning extension. Arrange accordingly for it not to be diagnosed with -std=c2x -pedantic, but to be diagnosed with -Wc11-c2x-compat. Bootstrapped with no regressions for x86_64-pc-linux-gnu. gcc/testsuite/ * gcc.dg/cpp/c11-warning-1.c,

[PATCH 05/10] [RISCV] Add %~ to print w if TARGET_64BIT and use it

From: Andrew Pinski To make things easier and more maintainable, we need to add support printing out w if TARGET_64BIT so this patch adds %~ to do that, similar how the x86 backend uses %~ to print out i/f for TARGET_AVX2. We could have chosen any punctuation symbol but ~ looks the closest to w.

[PATCH 07/10] [RISCV] Use a constraint for bset_mask and bset_1_mask

From: Andrew Pinski A constraint here just makes it easier to understand what the operands are. OK? Built and tested on riscv32-linux-gnu and riscv64-linux-gnu with --with-arch=rvNimafdc_zba_zbb_zbc_zbs (where N is 32 and 64). Thanks, Andrew Pinski gcc/ChangeLog: *

[PATCH 10/10] [RISCV] Fix PR 106632 and PR 106588 a few constraints in bitmanip.md

From: Andrew Pinski The constraints should be n instead of i. Also there needs to a check for out of bounds zero_extract for *bexti. gcc/ChangeLog: PR target/106632 PR target/106588 * config/riscv/bitmanip.md (*shNadduw): Use n constraint instead of i.

[PATCH 09/10] [RISCV] Add constraints for not_single_bit_mask_operand/single_bit_mask_operand

From: Andrew Pinski Like a previous patch, just add constraints for predicates not_single_bit_mask_operand and single_bit_mask_operand. OK? Built and tested for riscv32-linux-gnu and riscv64-linux-gnu. Thanks, Andrew Pinski gcc/ChangeLog: * config/riscv/constraints.md (DbS): New

[PATCH 08/10] [RISCV] Fix PR 106586: riscv32 vs ZBS

From: Andrew Pinski The problem here is two fold. With RISCV32, 32bit const_int are always signed extended to 64bit in HWI. So that means for SINGLE_BIT_MASK_OPERAND, it should mask off the upper bits to see it is a single bit for !TARGET_64BIT. Plus there are a few locations which forget to

[PATCH 06/10] [RISCV] Use constraints/predicates instead of checking const_int directly for shNadd patterns

From: Andrew Pinski This simplifies the code by adding a predicate and a constraint for 1/2/3. The aarch64 backend has a similar predicate called aarch64_shift_imm_ which they use there. OK? Built and tested on riscv32-linux-gnu and riscv64-linux-gnu with no regressions. Thanks, Andrew Pinski

[PATCH 01/10] [RISCV] Move iterators from riscv.md to iterators.md

From: Andrew Pinski This moves the iterators out from riscv.md to iterators.md like most modern backends. I have not moved the iterators from the other .md files yet. OK? Build and tested on riscv64-linux-gnu and riscv32-linux-gnu. Thanks, Andrew Pinski gcc/ChangeLog: *

[PATCH 03/10] [RISCV] Move iterators from sync.md to iterators.md

From: Andrew Pinski Like the previous two patches this moves the iterators that are in sync.md to iterators.md. OK? build and tested for riscv64-linux-gnu. gcc/ChangeLog: * config/riscv/sync.md (any_atomic, atomic_optab): Move to ... * config/riscv/iterators.md: Here. ---

[PATCH 02/10] [RISCV] Move iterators from bitmanip.md to iterators.md

From: Andrew Pinski Just like the previous patch this move all of the iterators of bitmanip.md to iterators.md. All modern backends put the iterators in iterators.md for easier access. OK? Built and tested for riscv32-linux-gnu with --with-arch=rv32imafdc_zba_zbb_zbc_zbs. Thanks, Andrew

[PATCH 04/10] [RISCV] Add the list of operand modifiers to riscv.md too

From: Andrew Pinski To make it easier to find operands modifiers while in the md file, add the list of modifiers to the top of the md file. This is similar to i386 target. OK? Built and tested for riscv32-linux-gnu and riscv64-linux-gnu. gcc/ChangeLog: * config/riscv/riscv.cc

[PATCH 00/10] [RISCV] Fix/improve the RISCV backend

From: Andrew Pinski This set of patches fixes a few RISCV issues and does a few cleanups. Including moving all of the iterators to iterators.md like many newer backends. It also fixes a few PRs which I filed including the RISCV32 issue with ZBS enabled. Thanks, Andrew Pinski Andrew Pinski

[PATCH] added myself to maintainers

--- ChangeLog | 4 MAINTAINERS | 2 ++ 2 files changed, 6 insertions(+) diff --git a/ChangeLog b/ChangeLog index 2c32b6403f0..a80db84157b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2022-08-18 Ondrej Kubanek + + * MAINTAINERS: add myself. + 2022-07-04 Martin Liska

[PATCH] Improve converting between 128-bit modes that use the same format

mprove converting between 128-bit modes that use the same format. This patch improves the insns used for converting between two modes using the 128-bit floating point format (i.e. converting between KFmode and TFmode if -mabi=ieeelongdouble is used, and converting between IFmode and TFmode if

[PATCH] Rework 128-bit complex multiply and divide.

Rework 128-bit complex multiply and divide. This function reworks how the complex multiply and divide built-in functions are done. Previously we created built-in declarations for doing long double complex multiply and divide when long double is IEEE 128-bit. The old code also did not support

[PATCH 3/3] Add 'w' suffix for __ibm128 constants

Add 'w' suffix for __ibm128 constants. In the documentation, we mention that 'w' or 'W' can be used as a suffix for __ibm128 constants. We never implemented this. This patch fixes that. In addition, the 'q' and 'Q' suffix were changed to use the mode used for the __float128 type, instead of

[PATCH 2/3] Allow __ibm128 with -msoft-float (PR target/105334)

Allow __ibm128 with -msoft-float (PR target/105334) This patch allows __ibm128 to be used on systems with software floating point enabled. Previously, we required hardware floating point to be enabled to use __ibm128 keyword and the __ibm128 built-in functions. This patch fixes PR

[PATCH 1/3] Allow __ibm128 even if IEEE 128-bit floating point is not supported.

Allow __ibm128 even if IEEE 128-bit floating point is not supported. This patch allows the use of the __ibm128 keyword on non-VSX systems. Originally, the __ibm128 keyword was only enabled when the IEEE 128-bit floating point is enabled. Sometime back in the GCC 12 development period, Segher

[PATCH 0/3] Improvements to __ibm128 on PowerPC

The following 3 patches improve __ibm128 on the PowerPC GCC compiler: The first patch allows the use of the __ibm128 keyword on non-VSX systems. Originally, the __ibm128 keyword was only enabled when the IEEE 128-bit floating point is enabled. Sometime back in the GCC 12 development period,

Re: [PATCH][DOCS] Document make jobserver related changes for GCC 13.

On Thu, 18 Aug 2022, Martin Liška wrote: > Ready for master? Nearly. :) > +Link-time optimization improvements: > + > +LTO supports the newly added GNU make's jobserver that uses > named pipes (--jobserver-style=fifo) I believe that's just "GNU make" (instead of "GNU make's"),

[PATCH] rs6000: Delete pr56605.c testcase

This testcase has never tested the problem in the PR it is named for (except perhaps very indirectly), and over the years this argumentation has become thinner all the time. Now we are faced with on the one hand having to accept various forms of code, but on the other hand very similar code is

[PATCH v2] c++: Implement -Wself-move warning [PR81159]

On Mon, Aug 15, 2022 at 03:54:05PM -0400, Jason Merrill wrote: > On 8/9/22 09:37, Marek Polacek wrote: > > + /* We're looking for *std::move ((T &) ), or > > + *std::move ((T &) (T *) r) if the argument it a reference. */ > > + if (!REFERENCE_REF_P (rhs) > > + || TREE_CODE

Re: [PATCH] xtensa: Improve indirect sibling call handling

On Thu, Aug 18, 2022 at 3:06 AM Takayuki 'January June' Suwa wrote: > > No longer needs the dedicated hard register (A11) for the address of the > call and the split patterns for fixups, due to the introduction of appropriate > register class and constraint. > > (Note: "ISC_REGS" contains a hard

Re: [PATCH, v2] Fortran: fix invalid rank error in ASSOCIATED when rank is remapped [PR77652]

Hi Mikael, all, I've just reverted commit 0110cfd5449bae3a772f45ea2e4c5dab5b7a8ccd. As it seems that commit ca170ed9f8a086ca7e1eec841882b6bed9ec1a3a did not update bugzilla, I'll add a note to the PR and close it as invalid. Thanks, Harald Am 04.08.22 um 14:03 schrieb Mikael Morin: Le

Re: [PATCH v3] rs6000: Rework ELFv2 support for -fpatchable-function-entry* [PR99888]

Hi! On Thu, Aug 18, 2022 at 10:12:48AM +0800, Kewen.Lin wrote: > As PR99888 and its related show, the current support for > -fpatchable-function-entry on powerpc ELFv2 doesn't work > well with global entry existence. > + /* Emit the NOPs after local entry. */ Please do not say "NOPs". It

[PATCH] Remove path_range_query constructor that takes an edge.

The path_range_query constructor that takes an edge is really a convenience function for the loop-ch pass. It feels wrong to pollute the API with such a specialized function that could be done with a small inline function closer to its user. As an added benefit, we remove one use of reset_path.

Re: [PING][PATCH] RISC-V: Standardize formatting of SFB ALU conditional move

On Thu, 18 Aug 2022, Kito Cheng wrote: > OK, thanks for tweaking this! Committed now, thanks for your review! Would you mind sharing your opinion on my previous observation here: ? I have since realised we have a

[PATCH] contrib: Fix a typo in contrib/git-fetch-vendor.sh

Hi all, just commited this to fix a typo as obvious. Bests Andrea /contrib/ChangeLog: * git-fetch-vendor.sh : Fix typo. diff --git a/contrib/git-fetch-vendor.sh b/contrib/git-fetch-vendor.sh index 15303629b5c..bbd52fb2055 100755 --- a/contrib/git-fetch-vendor.sh +++

Re: [PATCH V2] Add warning options -W[no-]compare-distinct-pointer-types

On Thu, 18 Aug 2022, Jose E. Marchesi via Gcc-patches wrote: > diff --git a/gcc/c/c-typeck.cc b/gcc/c/c-typeck.cc > index de8780a1502..04af02add37 100644 > --- a/gcc/c/c-typeck.cc > +++ b/gcc/c/c-typeck.cc > @@ -12397,7 +12397,8 @@ build_binary_op (location_t location, enum tree_code > code, >

Re: [GCC][PATCH v2] arm: Add support for Arm Cortex-M85 CPU.

On 12/08/2022 18:20, Srinath Parvathaneni via Gcc-patches wrote: Hi, This patch adds the -mcpu support for the Arm Cortex-M85 CPU which is an Armv8.1-M Mainline CPU supporting MVE and PACBTI by default. -mpcu=cortex-m85 switch by default matches to

Re: [PING][PATCH] RISC-V: Standardize formatting of SFB ALU conditional move

OK, thanks for tweaking this! On Thu, Aug 18, 2022 at 10:40 PM Maciej W. Rozycki wrote: > > On Tue, 26 Jul 2022, Maciej W. Rozycki wrote: > > > Standardize the formatting of SFB ALU conditional move operations from: > > > > beq a2,zero,1f; mv a0,zero; 1: # movcc > > > > to: > > > >

Re: [PATCH] Fix bogus -Wstringop-overflow warning in Ada

> Hmm :/ But that means we _should_ force a sign extension but only > from ptrofftype_p ()? That is, your test above should maybe read > >signop sgn = TYPE_SIGN (type); >if (ptrofftype_p (type)) > sgn = SIGNED; > > assuming 'type' is the type of lowbnd Yes, that's essentially

[PING][PATCH] RISC-V: Standardize formatting of SFB ALU conditional move

On Tue, 26 Jul 2022, Maciej W. Rozycki wrote: > Standardize the formatting of SFB ALU conditional move operations from: > > beq a2,zero,1f; mv a0,zero; 1: # movcc > > to: > > beq a2,zero,1f # movcc > mv a0,zero > 1: > > for consistency with other assembly code

[PATCH] Improve uninit analysis

The following reduces the number of false positives in uninit analysis by providing fallback for situations the current analysis gives up and thus warns because it cannot prove initialization. The first situation is when compute_control_dep_chain gives up walking because it runs into either

[PATCH] middle-end/106617 - fix fold_binary_op_with_conditional_arg pattern issue

Now that we have parts of fold_binary_op_with_conditional_arg duplicated in match.pd and are using ! to take or throw away the result we have to be careful to not have both implementations play games which each other, causing quadratic behavior. In particular the match.pd implementation requires

Re: [PATCH] Support threading of just the exit edge

On 8/18/22 03:08, Richard Biener wrote: The caveat is that it is only a partial solution... it will only work for names on that stmt.  if you have anything more complex, ie if (a == 0 || b == 0)  we have a seqeunce feeding the ctrl stmt.. c_1 = a == 0 c_2 = b == 0 c_3 = c_1 && c_2 if (c_3

Re: [PATCH V2] place `const volatile' objects in read-only sections

ping > [Changes from V1: > - Added a test.] > > It is common for C BPF programs to use variables that are implicitly > set by the BPF loader and run-time. It is also necessary for these > variables to be stored in read-only storage so the BPF verifier > recognizes them as such. This leads to

[PATCH V2] Add warning options -W[no-]compare-distinct-pointer-types

Hi Joseph. > On Fri, 5 Aug 2022, Jose E. Marchesi via Gcc-patches wrote: > >> +Wcompare-distinct-pointer-types >> +C C++ Var(warn_compare_distinct_pointer_types) Warning Init(1) >> +Warn if pointers of distinct types are compared without a cast. > > There's no implementation for C++ in this

Re: [PATCH v1] LoongArch: Add support code model extreme.

在 2022/8/18 下午8:52, Xi Ruoyao 写道: On Thu, 2022-08-18 at 19:49 +0800, Lulu Cheng wrote: I think we can ignore the effect of -fplt if code model is extreme, instead of forcing everyone to explicitly add -fno-plt. The "large" code model of x86_64 also does not limit the address range and it

Re: [PATCH v1] LoongArch: Add support code model extreme.

On Thu, 2022-08-18 at 19:49 +0800, Lulu Cheng wrote: > > I think we can ignore the effect of -fplt if code model is extreme, > > instead of forcing everyone to explicitly add -fno-plt. The "large" > > code model of x86_64 also does not limit the address range and it always > > avoids PLT (even if

Re: ICE after folding svld1rq to vec_perm_expr duing forwprop

On Thu, 18 Aug 2022 at 18:14, Prathamesh Kulkarni wrote: > > On Wed, 17 Aug 2022 at 17:01, Richard Biener > wrote: > > > > On Tue, Aug 16, 2022 at 6:30 PM Richard Sandiford > > wrote: > > > > > > Prathamesh Kulkarni writes: > > > > On Tue, 9 Aug 2022 at 18:42, Richard Biener > > > > wrote:

Re: ICE after folding svld1rq to vec_perm_expr duing forwprop

On Wed, 17 Aug 2022 at 17:01, Richard Biener wrote: > > On Tue, Aug 16, 2022 at 6:30 PM Richard Sandiford > wrote: > > > > Prathamesh Kulkarni writes: > > > On Tue, 9 Aug 2022 at 18:42, Richard Biener > > > wrote: > > >> > > >> On Tue, Aug 9, 2022 at 12:10 PM Prathamesh Kulkarni > > >>

[PATCH] jobserver: detect properly O_NONBLOCK

That handles systems that don't have O_NONBLOCK, in that case WPA streaming is not using jobserver if --jobserver-auth uses 'fifo'. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Tested with mingw cross compiler as well. Ready to be installed? Thanks, Martin

Re: [PATCH v2] analyzer: warn on the use of floating-points operands in the size argument [PR106181]

On Thu, 2022-08-18 at 11:44 +0200, Tim Lange wrote: > Hi, > > this is the revised version of my patch. I had trouble to get your > point regarding the float_visitor: > > > If the constant is seen first, then the non-constant won't be > > favored > > (though perhaps binary ops get canonicalized

Re: [PATCH v1] LoongArch: Add support code model extreme.

在 2022/8/18 下午7:37, Xi Ruoyao 写道: + if (opts->x_flag_plt) + error ("code model %qs and %qs not support %s mode", +"tiny-static", "extreme", "plt"); I think we can ignore the effect of -fplt if code model is extreme, instead of forcing everyone to explicitly add

Re: [PATCH v1] LoongArch: Add support code model extreme.

On Thu, 2022-08-18 at 18:01 +0800, Lulu Cheng wrote: > Use five instructions to calculate a signed 64-bit offset relative to the pc. > gcc/ChangeLog: > > * config/loongarch/loongarch-opts.cc: Allow cmodel to be extreme. > * config/loongarch/loongarch.cc

[PATCH][DOCS] Document make jobserver related changes for GCC 13.

Ready for master? --- htdocs/gcc-13/changes.html | 9 + 1 file changed, 9 insertions(+) diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 57bd8724..95fee90d 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -52,6 +52,15 @@ a

Re: [PATCH] Make path_range_query standalone and add reset_path.

On Thu, Aug 18, 2022, 11:34 Richard Biener wrote: > > On Thu, Aug 18, 2022 at 9:58 AM Aldy Hernandez wrote: > > > > FWIW, here is a rebased version with the latest trunk. > > > > There are no regressions, or differences in threading counts, and the > > performance change is negligible. > > +

[PATCH] middle-end: skipp stepped vector test of poly_int (1, 1) and allow the machine_mode definition with poly_uint16 (1, 1)

From: zhongjuzhe Hello. This patch is preparing for following RVV support. Both ARM SVE and RVV (RISC-V 'V' Extension) support length-agnostic vector. The minimum vector length of ARM SVE is 128-bit and the runtime invariant of ARM SVE is always 128-bit blocks. However, the minimum vector

Re: [PATCH] fortran, v2: Add -static-libquadmath support [PR46539]

On Thu, Aug 18, 2022 at 11:35:06AM +0100, Iain Sandoe wrote: > > --- gcc/fortran/options.cc.jj 2022-01-18 11:58:59.568982256 +0100 > > +++ gcc/fortran/options.cc 2022-08-16 14:56:22.807525218 +0200 > > @@ -692,6 +692,13 @@ gfc_handle_option (size_t scode, const c > > #endif > > break;

[PATCH (pushed)] build: regenerate gcc/configure

After the change 71f068a9b3332a2179dfc807cf9138f691d77461, gcc/configure needs to re-generated. gcc/ChangeLog: * configure: Regenerate. --- gcc/configure | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/gcc/configure b/gcc/configure index

Re: [PATCH, GCC, AARCH64, 5/6] Enable BTI : Add new pass for BTI.

On 18/08/2022 01:00, Andrew Pinski via Gcc-patches wrote: On Fri, Nov 2, 2018 at 11:39 AM Sudakshina Das wrote: Hi This patch is part of a series that enables ARMv8.5-A in GCC and adds Branch Target Identification Mechanism.

[PATCH] xtensa: Improve indirect sibling call handling

No longer needs the dedicated hard register (A11) for the address of the call and the split patterns for fixups, due to the introduction of appropriate register class and constraint. (Note: "ISC_REGS" contains a hard register A8 used as a "static chain" pointer for nested functions, but no

[PATCH v1] LoongArch: Add support code model extreme.

Use five instructions to calculate a signed 64-bit offset relative to the pc. gcc/ChangeLog: * config/loongarch/loongarch-opts.cc: Allow cmodel to be extreme. * config/loongarch/loongarch.cc (loongarch_call_tls_get_addr): Add extreme support for TLS GD and LD types.

[PATCH v2] analyzer: warn on the use of floating-points operands in the size argument [PR106181]

Hi, this is the revised version of my patch. I had trouble to get your point regarding the float_visitor: > If the constant is seen first, then the non-constant won't be favored > (though perhaps binary ops get canonicalized so that constants are on > the RHS?). Only the assignment of m_result

Re: [PATCH] Make path_range_query standalone and add reset_path.

On Thu, Aug 18, 2022 at 9:58 AM Aldy Hernandez wrote: > > FWIW, here is a rebased version with the latest trunk. > > There are no regressions, or differences in threading counts, and the > performance change is negligible. +{ + mark_dfs_back_edges (); + + if (flag_checking) +

Re: [PATCH] Fix bogus -Wstringop-overflow warning in Ada

On Thu, Aug 18, 2022 at 9:54 AM Eric Botcazou wrote: > > > Meh. OK, eventually would need "indirection" through a wide-int then. > > Like > > > > offset_int::from (wi::to_wide (lowbnd), TYPE_SIGN (TREE_TYPE (lowbnd))) > > That would be OK if get_offset_range did the same, but it does not since

[PATCH] libcpp, v2: Implement C++23 P2290R3 - Delimited escape sequences [PR106645]

On Wed, Aug 17, 2022 at 10:22:03PM -0400, Jason Merrill wrote: > OK, a comment mentioning this should be sufficient. Here is an updated patch with those changes in. So far successfully tested with GXX_TESTSUITE_STDS=98,11,14,17,20,2b make -j32 -k check-gcc check-g++ RUNTESTFLAGS="dg.exp='Wbidi*

Re: [PATCH] Make path_range_query standalone and add reset_path.

FWIW, here is a rebased version with the latest trunk. There are no regressions, or differences in threading counts, and the performance change is negligible. Aldy On Wed, Aug 17, 2022 at 1:59 PM Aldy Hernandez wrote: > > These are a bunch of cleanups inspired by Richi's suggestion of making >

Re: [PATCH] Fix bogus -Wstringop-overflow warning in Ada

> Meh. OK, eventually would need "indirection" through a wide-int then. > Like > > offset_int::from (wi::to_wide (lowbnd), TYPE_SIGN (TREE_TYPE (lowbnd))) That would be OK if get_offset_range did the same, but it does not since it forces a sign-extension whatever the sign of a large type:

Re: [PATCH] wwwdocs: Add D language changes and caveats to gcc-12/changes.html

On Wed, Aug 17, 2022 at 7:24 PM Iain Buclaw via Gcc-patches wrote: > > Hi, > > This patch belatedly adds the new features and changes to the D > front-end during the GCC 12 development cycle, as well as a bullet in > the caveat section for D's new bootstrapping requirements. > > If nothing stands

[PATCH] Add ABI test for __bf16 type

Hi all, This patch aims to add bf16 abi test after the whole __bf16 type is added. Regtested on x86_64-pc-linux-gnu. Ok for trunk? BRs, Haochen gcc/testsuite/ChangeLog: * gcc.target/x86_64/abi/bf16/abi-bf16.exp: New test. * gcc.target/x86_64/abi/bf16/args.h: Ditto. *

Re: [PATCH] Add further FOR_EACH_ macros

On Wed, Aug 17, 2022 at 3:56 PM Stefan Schulze Frielinghaus via Gcc-patches wrote: > > For my current use case only some FOR_EACH_MODE macros were missing. > Though I thought I will give it a try and grep'ed through the source > code and added further ones. I didn't manually check all of them

Re: [PATCH] Fix bogus -Wstringop-overflow warning in Ada

On Wed, Aug 17, 2022 at 3:38 PM Eric Botcazou wrote: > > > Hmm, can we instead do > > > > if (!integer_zerop (lowbnd) && tree_fits_shwi_p (lowbnd)) > >{ > > const offset_int lb = offset_int::from (lowbnd, SIGNED); > > ... > > > > ? > > Apparently not: > > In file included from

Re: [COMMITTED] Abstract interesting ssa-names from GORI.

Thanks. Pushed. On Wed, Aug 17, 2022 at 3:18 AM Andrew MacLeod wrote: > > > On 8/16/22 21:16, Andrew MacLeod wrote: > > > > On 8/16/22 04:21, Aldy Hernandez wrote: > >> On Thu, Aug 11, 2022 at 1:42 PM Richard Biener > >> wrote: > >> > >>> @@ -599,6 +592,30 @@ path_range_query::compute_imports

Re: [PATCH] Makefile.def: drop remnants of unused libelf

On Thu, Aug 18, 2022 at 9:07 AM Sergei Trofimovich via Gcc-patches wrote: > > From: Sergei Trofimovich > > Use of libelf was removed from gcc in > misc/cutover-cvs2svn-32781-g48215350c24 ("re PR lto/46273 (Failed to > bootstrap)") around 2010, before gcc-4.6.0. > > This change removes unused

Re: [PATCH] Support threading of just the exit edge

On Wed, 17 Aug 2022, Andrew MacLeod wrote: > > On 8/17/22 03:42, Richard Biener wrote: > > On Tue, 16 Aug 2022, Andrew MacLeod wrote: > > > >> On 8/16/22 05:18, Richard Biener wrote: > >>> On Mon, 15 Aug 2022, Aldy Hernandez wrote: > >>> > On Mon, Aug 15, 2022 at 9:24 PM Andrew MacLeod >

[PATCH] Makefile.def: drop remnants of unused libelf

From: Sergei Trofimovich Use of libelf was removed from gcc in misc/cutover-cvs2svn-32781-g48215350c24 ("re PR lto/46273 (Failed to bootstrap)") around 2010, before gcc-4.6.0. This change removes unused references to libelf from top-level condifure and Makefile. / * Makefile.def: Drop

[PATCH] Add libgo dependency on libbacktrace.

From: Sergei Trofimovich Noticed missing dependency when regenerated Makefile.in for unrelated change with 'autoget Makefile.def'. The change was lost in basepoints/gcc-12-6861-gaeac414923a ("Revert "Fix PR 67102: Add libstdc++ dependancy to libffi" [PR67102]"). / Makefile.in:

[PATCH] Enhance final_value_replacement_loop to handle bitop with an invariant induction.[PR105735]

Hi, This patch is for pr105735/pr101991. It will enable below optimization: { - long unsigned int bit; - - [local count: 32534376]: - - [local count: 1041207449]: - # tmp_10 = PHI - # bit_12 = PHI - tmp_7 = bit2_6(D) & tmp_10; - bit_8 = bit_12 + 1; - if (bit_8 != 32) -goto ;

Re: [PATCH] PR106342 - IBM zSystems: Provide vsel for all vector modes

On Wed, 17 Aug 2022, Ilya Leoshkevich wrote: > On Thu, 2022-08-11 at 07:45 +0200, Andreas Krebbel wrote: > > On 8/10/22 13:42, Ilya Leoshkevich wrote: > > > On Wed, 2022-08-03 at 12:20 +0200, Ilya Leoshkevich wrote: > > > > Bootstrapped and regtested on s390x-redhat-linux.  Ok for master? > > > >