Re: [PATCH] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS

2022-08-28 Thread Jan-Benedict Glaw
On Tue, 2021-09-21 16:25:19 +0200, Richard Biener via Gcc-patches wrote: > This makes defaults.h choose DWARF2_DEBUG if PREFERRED_DEBUGGING_TYPE > is not specified by the target and errors out if DWARF DWARF is not supported. While I think the pdp11 bits arreved, the rest did not (yet). Just che

[PATCH] nvptx: Silence unused variable warning

2022-08-28 Thread Jan-Benedict Glaw
Hi! The nvptx backend defines ASM_OUTPUT_DEF along with ASM_OUTPUT_DEF_FROM_DECLS. Much like the rs6000 coff target, nvptx triggers an unused variable warning: /usr/lib/gcc-snapshot/bin/g++ -fno-PIE -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous

Re: [PATCH] 32-bit PA-RISC with HP-UX: remove deprecated ports

2022-08-28 Thread John David Anglin
On 2022-08-26 3:15 a.m., Martin Liška wrote: Removes the deprecated ports. If I'm correct all hpux9,hpux10 should be removed as they only provide 32-bit targets. On the contrary, hpux11 supports hppa64 that we still do support. It is my understanding that the 32-bit hppa hpux targets were depre

Re: [PATCH] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS

2022-08-28 Thread Jeff Law via Gcc-patches
On 8/28/2022 1:50 AM, Jan-Benedict Glaw wrote: On Tue, 2021-09-21 16:25:19 +0200, Richard Biener via Gcc-patches wrote: This makes defaults.h choose DWARF2_DEBUG if PREFERRED_DEBUGGING_TYPE is not specified by the target and errors out if DWARF DWARF is not supported. While I think the pdp

Re: [PATCH] x86: Cast stride to __PTRDIFF_TYPE__ in AMX intrinsics

2022-08-28 Thread Hongtao Liu via Gcc-patches
On Sat, Aug 27, 2022 at 12:51 AM H.J. Lu wrote: > > On Mon, Aug 22, 2022 at 7:05 PM Hongtao Liu wrote: > > > > On Tue, Aug 23, 2022 at 1:02 AM H.J. Lu wrote: > > > > > > On 64-bit Windows, long is 32 bits and can't be used as stride in memory > > > operand when base is a pointer which is 64 bits

[PATCH] libstdc++: Introduce GNU/Hurd-specific libstdc++ os-defines.h

2022-08-28 Thread Samuel Thibault via Gcc-patches
This is notably needed because in glibc 2.34, the move of pthread functions into libc.so happened for Linux only, not GNU/Hurd. The pthread_self() function can also always be used fine as it is. libstdc++-v3/ChangeLog: * config/os/gnu/os_defines.h: New file. * config/os/gnu/ctype

Re: [PATCH] RISC-V: Add RVV instructions classification

2022-08-28 Thread Kito Cheng via Gcc-patches
Committed, thanks! On Sat, Aug 27, 2022 at 6:58 PM wrote: > > From: zhongjuzhe > > gcc/ChangeLog: > > * config/riscv/riscv.md: Add new type for vector instructions. > > --- > gcc/config/riscv/riscv.md | 100 +- > 1 file changed, 99 insertions(+), 1 de

Re: [PATCH] RISC-V: Add RVV registers

2022-08-28 Thread Kito Cheng via Gcc-patches
Committed, thanks! On Sat, Aug 27, 2022 at 7:09 PM wrote: > > From: zhongjuzhe > > gcc/ChangeLog: > > * config/riscv/riscv.cc (riscv_v_ext_vector_mode_p): New function. > (riscv_classify_address): Disallow PLUS/LO_SUM/CONST_INT address > types for RVV. > (riscv_address_i

[committed] RISC-V: Suppress -Wclass-memaccess warning

2022-08-28 Thread Kito Cheng
poly_int64 is non-trivial type, we need to clean up manully instead of memset to prevent this warning. ../../gcc/gcc/config/riscv/riscv.cc: In function 'void riscv_compute_frame_info()': ../../gcc/gcc/config/riscv/riscv.cc:4113:10: error: 'void* memset(void*, int, size_t)' clearing an object of

[PATCH V0] RISC-V: Fix a redefinition bug for the fd-4.c

2022-08-28 Thread shiyulong
From: yulong This patch fix a redefinition bug. There are have a definition about mode_t in the fd-4.c, but it duplicates the definition in stdio.h. gcc/testsuite/ChangeLog: * gcc.dg/analyzer/fd-4.c: delete the definition of mode_t. --- gcc/testsuite/gcc.dg/analyzer/fd-4.c | 5 -

Re: [PATCH] LoongArch: testsuite: refine __tls_get_addr tests with tls_native

2022-08-28 Thread Lulu Cheng
LGTM! Thanks. 在 2022/8/24 下午10:09, Xi Ruoyao 写道: If GCC is not built with a working linker for the target (developers occansionally build such a "minimal" GCC for testing and debugging), TLS will be emulated and __tls_get_addr won't be used. Refine those tests depending on __tls_get_addr with

[PATCH V6] rs6000: Optimize cmp on rotated 16bits constant

2022-08-28 Thread Jiufu Guo via Gcc-patches
Hi, When checking eq/ne with a constant which has only 16bits, it can be optimized to check the rotated data. By this, the constant building is optimized. As the example in PR103743: For "in == 0x8000LL", this patch generates: rotldi %r3,%r3,16 cmpldi %cr0,%r3,32768 i

Re: [PATCH V2]HIGH part of symbol ref is invalid for constant pool[PR106460]

2022-08-28 Thread Jiufu Guo via Gcc-patches
Jiufu Guo writes: New patch V6 is updated as: https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600475.html. BR, Jeff(Jiufu) > Hi, > > As the issue in PR106460, a rtx 'high:DI (symbol_ref:DI ("var_48")' is tried > to store into constant pool. But actually, it indicates partial address, > w

[PATCH V2] Extend vectorizer to handle nonlinear induction for neg, mul/lshift/rshift with a constant.

2022-08-28 Thread liuhongt via Gcc-patches
>Looks good overall - a few comments inline. Also can you please add >SLP support? >I've tried hard to fill in gaps where SLP support is missing since my >goal is still to get >rid of non-SLP. For slp with different induction type, they need separate iv update and an vector permutation. And if the

Re: Extend fold_vec_perm to fold VEC_PERM_EXPR in VLA manner

2022-08-28 Thread Prathamesh Kulkarni via Gcc-patches
On Wed, 17 Aug 2022 at 18:09, Prathamesh Kulkarni wrote: > > Hi, > The attached prototype patch extends fold_vec_perm to fold VEC_PERM_EXPR > in VLA manner, and currently handles the following cases: > (a) fixed len arg0, arg1 and fixed len sel. > (b) fixed len arg0, arg1 and vla sel > (c) vla arg

Re: [PATCH, rs6000] Put dg-options ahead of target selector checks

2022-08-28 Thread Kewen.Lin via Gcc-patches
Hi Haochen, on 2022/8/26 15:29, HAO CHEN GUI wrote: > Hi, > This patch changes the sequence of test directives for 3 cases. Originally, > these 3 cases got failed or unsupported on some platforms, as their target > selector checks depend on compiling options. Maybe it's good to say more in the

PING^2 [PATCH v2] rs6000/test: Fix empty TU in some cases of effective targets [PR106345]

2022-08-28 Thread Kewen.Lin via Gcc-patches
Hi, Gentle ping this: https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598748.html BR, Kewen > on 2022/7/25 14:26, Kewen.Lin via Gcc-patches wrote: >> Hi, >> >> As the failure of test case gcc.target/powerpc/pr92398.p9-.c in >> PR106345 shows, some test sources for some powerpc effective >>

PING^2 [PATCH] rs6000: Suggest unroll factor for loop vectorization

2022-08-28 Thread Kewen.Lin via Gcc-patches
Hi, Gentle ping: https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598601.html BR, Kewen > > on 2022/7/20 17:30, Kewen.Lin via Gcc-patches wrote: >> Hi, >> >> Commit r12-6679-g7ca1582ca60dc8 made vectorizer accept one >> unroll factor to be applied to vectorization factor when >> vectorizing

Re: ICE after folding svld1rq to vec_perm_expr duing forwprop

2022-08-28 Thread Prathamesh Kulkarni via Gcc-patches
On Thu, 18 Aug 2022 at 18:20, Prathamesh Kulkarni wrote: > > 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

PING^5 [PATCH] rs6000: Handle unresolved overloaded builtin [PR105485]

2022-08-28 Thread Kewen.Lin via Gcc-patches
Hi, Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594699.html I think this is a reasonable fix, the behavior is consistent with what we have in the previous built-in framework, I'm going to push this a week later if no objections. :) BR, Kewen >>> on 2022/5/13 13:29, Ke

PING^5 [PATCH v3] rs6000: Fix the check of bif argument number [PR104482]

2022-08-28 Thread Kewen.Lin via Gcc-patches
Hi, Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595208.html I think this is a reasonable fix, the behavior is consistent with what we have in the previous built-in framework, I'm going to push this a week later if no objections. :) BR, Kewen > Hi, > > As PR104

Re: [PATCH] predict: Adjust optimize_function_for_size_p [PR105818]

2022-08-28 Thread Kewen.Lin via Gcc-patches
on 2022/8/15 16:33, Kewen.Lin via Gcc-patches wrote: > on 2022/7/11 11:42, Kewen.Lin wrote: >> on 2022/6/15 14:20, Kewen.Lin wrote: >>> Hi Honza, >>> >>> Thanks for the comments! Some replies are inlined below. >>> >>> on 2022/6/14 19:37, Jan Hubicka wrote: > Hi, > > Function optimize_