[PATCH] RISC-V: Add Z*inx incompatible check in gcc.

2023-03-26 Thread Jiawei
Z*inx is conflict with float extensions, add incompatible check when z*inx and hard_float both enabled. gcc/ChangeLog: * config/riscv/riscv.cc (riscv_option_override): New check. --- gcc/config/riscv/riscv.cc | 4 1 file changed, 4 insertions(+) diff --git a/gcc/config/riscv/riscv

[pushed] doc: Remove anachronistic note related to languages built

2023-03-26 Thread Gerald Pfeifer
Jonathan's patch https://gcc.gnu.org/pipermail/gcc-patches/2022-November/604796.html lat November made me have a look for further instances, and indeed there was another one referring to separate tarballs (which we have not been shipping for a fair bit). Since the item above already refers to `

[wwwdocs] Add Ada's GCC13 changelog entry

2023-03-26 Thread Fernando Oleo Blanco via Gcc-patches
Hi all, a bit belated but just like last year, I've made a patch for the Ada entry in the changelog. You can find the patch attached to this email. If I have forgotten anything relevant or if I have done something incorrectly, please, say so. Best regards, Fernando Oleo BlancoFrom d273bb1835c1ef

[PATCH] c++, coroutines: Stabilize names of promoted slot vars [PR101118].

2023-03-26 Thread Iain Sandoe via Gcc-patches
Tested on x86_64-darwin21, x86-64-linux-gnu OK for trunk? Iain When we need to 'promote' a value (i.e. store it in the coroutine frame) it is given a frame entry name. This was based on the DECL_UID for slot vars. However, when LTO is used, the names from multiple TUs become visible at the same t

Re: [PATCH] predict: Don't emit -Wsuggest-attribute=cold warning for functions which already have that attribute [PR105685]

2023-03-26 Thread Jeff Law via Gcc-patches
On 3/25/23 03:53, Jakub Jelinek via Gcc-patches wrote: Hi! In the following testcase, we predict baz to have cold entry regardless of the user supplied attribute (as it call unconditionally a cold function), but still issue a -Wsuggest-attribute=cold warning despite it having that attribute a

Re: [PATCH] tree-optimization/109237 - last_stmt is possibly slow

2023-03-26 Thread Jeff Law via Gcc-patches
On 3/22/23 06:29, Richard Biener via Gcc-patches wrote: Most uses of last_stmt are interested in control transfer stmts and for the testcase gimple_purge_dead_eh_edges shows up in the profile. But last_stmt looks past trailing debug stmts but those would be rejected by GIMPLEs verify_flow_inf

Re: [PATCH] match.pd: Fix up fneg/fadd simplification [PR109230]

2023-03-26 Thread Jeff Law via Gcc-patches
On 3/22/23 04:16, Jakub Jelinek via Gcc-patches wrote: Hi! The following testcase is miscompiled on aarch64-linux. match.pd has a simplification for addsub, where it negates one of the vectors in twice as large floating point element vector (effectively negating every other element) and then

Re: [PATCH] rtl-optimization/109237 - speedup bb_is_just_return

2023-03-26 Thread Jeff Law via Gcc-patches
On 3/22/23 04:03, Richard Biener via Gcc-patches wrote: For the testcase bb_is_just_return is on top of the profile, changing it to walk BB insns backwards puts it off the profile. That's because in the forward walk you have to process possibly many debug insns but in a backward walk you very

Re: [PATCH, commited] Fortran: remove dead code [PR104321]

2023-03-26 Thread Harald Anlauf via Gcc-patches
Hi Paul,   > If you will excuse the British cultural reference, that's a Norwegian Blue > alright! Good spot.   ROTFL! I first had to look up the "Norwegian Blue", and then I remembered. :) You're bringing back the fun to gfortran hacking! Cheers, Harald    On Sat, 25 Mar 2023 at 19:13, Haral

Re: [PATCH] predict: Don't emit -Wsuggest-attribute=cold warning for functions which already have that attribute [PR105685]

2023-03-26 Thread Jan Hubicka via Gcc-patches
> Hi! > > In the following testcase, we predict baz to have cold > entry regardless of the user supplied attribute (as it call > unconditionally a cold function), but still issue > a -Wsuggest-attribute=cold warning despite it having that attribute > already. > > The following patch avoids that.

m68k: handle TLS access with offset

2023-03-26 Thread Andreas Schwab
This reinstates FINAL_PRESCAN_INSN, and the calls in handle_move_double, so that access to TLS variables with offset are properly handled. gcc: PR target/106282 * config/m68k/m68k.h (FINAL_PRESCAN_INSN): Define. * config/m68k/m68k.cc (m68k_final_prescan_insn): Define.

Re: Re: [PATCH] RISC-V: Optimize zbb ins sext.b and sext.h in rv64

2023-03-26 Thread Feng Wang
On 2023-03-26 02:18  Jeff Law wrote: > > > >On 3/23/23 20:45, juzhe.zh...@rivai.ai wrote: >> Sounds like you are looking at redundant extension problem in RISC-V port. >> This is the issue I want to fix but I don't find the time to do that. >> My first impression is that we need to fix redundant ex

Re: [PATCH] RTL: Bugfix for wrong code with v16hi compare & mask

2023-03-26 Thread Hongtao Liu via Gcc-patches
On Sun, Mar 26, 2023 at 3:01 AM Jeff Law via Gcc-patches wrote: > > > > On 3/24/23 08:11, pan2.li--- via Gcc-patches wrote: > > From: Pan Li > > > > Fix the bug of the incorrect code generation for the > > below code sample. > > > > typedef unsigned short __attribute__((__vector_size__ (32))) V;

Re: [PATCH] RISC-V: Optimize zbb ins sext.b and sext.h in rv64

2023-03-26 Thread Jeff Law via Gcc-patches
On 3/26/23 19:32, Feng Wang wrote: On 2023-03-26 02:18  Jeff Law wrote: On 3/23/23 20:45, juzhe.zh...@rivai.ai wrote: Sounds like you are looking at redundant extension problem in RISC-V port. This is the issue I want to fix but I don't find the time to do that. My first impression is tha

[PATCH, rs6000] rs6000: correct vector sign extend built-ins on Big Endian [PR108812]

2023-03-26 Thread HAO CHEN GUI via Gcc-patches
Hi, This patch removes byte reverse operation before vector integer sign extension on Big Endian. These built-ins require to sign extend the rightmost element. So both BE and LE should do the same operation and the byte reversion is no need. This patch fixes it. Now these built-ins have the same

Re: [PATCH] c++, coroutines: Stabilize names of promoted slot vars [PR101118].

2023-03-26 Thread Richard Biener via Gcc-patches
On Sun, Mar 26, 2023 at 6:55 PM Iain Sandoe via Gcc-patches wrote: > > Tested on x86_64-darwin21, x86-64-linux-gnu > OK for trunk? > Iain > > When we need to 'promote' a value (i.e. store it in the coroutine frame) it > is given a frame entry name. This was based on the DECL_UID for slot vars. >

Re: [PATCH] lto/109263 - lto-wrapper and -g0 -ggdb

2023-03-26 Thread Richard Biener via Gcc-patches
On Thu, 23 Mar 2023, Richard Biener wrote: > The following makes lto-wrapper deal with non-combined debug > disabling / enabling option combinations properly. Interestingly > -gno-dwarf also enables debug. > > Bootstrap / regtest running on x86_64-unknown-linux-gnu. > > OK? Or do we want to tr

Re: [PATCH] c++, coroutines: Stabilize names of promoted slot vars [PR101118].

2023-03-26 Thread Iain Sandoe
Hi Richard, (I’m away from my usual infrastructure, so responses could be slow and testing things could take a while). > On 27 Mar 2023, at 12:10, Richard Biener wrote: > > On Sun, Mar 26, 2023 at 6:55 PM Iain Sandoe via Gcc-patches > wrote: >> >> Tested on x86_64-darwin21, x86-64-linux-gnu >

[PATCH] RISC-V: Fix PR108279

2023-03-26 Thread juzhe . zhong
From: Juzhe-Zhong PR 108270 Fix bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108270. Consider the following testcase: void f (void * restrict in, void * restrict out, int l, int n, int m) { for (int i = 0; i < l; i++){ for (int j = 0; j < m; j++){ for (int k = 0; k < n;