[Bug target/110588] btl (on x86_64) not always generated

2023-07-22 Thread roger at nextmovesoftware dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110588 Roger Sayle changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/110066] [13 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 Andrew Pinski changed: What|Removed |Added Known to work||12.3.0, 14.0 Summary|[13/14

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #22 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:bbc1a102735c72e3c5a4dede8ab382813d12b058 commit r14-2733-gbbc1a102735c72e3c5a4dede8ab382813d12b058 Author: Andrew Pinski Date:

Re: Re: [PATCH V2] VECT: Support floating-point in-order reduction for length loop control

2023-07-22 Thread Lehua Ding
Hi Richard, Bootstrap and regression are passed on X86 and no new testcases fail on AArch64 with V5 patch: https://gcc.gnu.org/pipermail/gcc-patches/2023-July/625293.html V5 patch is ok for trunk? Best, Lehua

[PATCH V5] VECT: Support floating-point in-order reduction for length loop control

2023-07-22 Thread Lehua Ding
From: Ju-Zhe Zhong PS: Submitted on behalf of Juzhe Zhong Hi, Richard and Richi. This patch support floating-point in-order reduction for loop length control. Consider this following case: float foo (float *__restrict a, int n) { float result = 1.0; for (int i = 0; i < n; i++) result

Re: [PATCH 1/2] Fix PR 110066: crash with -pg -static on riscv

2023-07-22 Thread Kito Cheng via Gcc-patches
OK for trunk, thanks:) Andrew Pinski via Gcc-patches 於 2023年7月23日 週日 09:07 寫道: > The problem -fasynchronous-unwind-tables is on by default for riscv linux > We need turn it off for crt*.o because it would make __EH_FRAME_BEGIN__ > point > to .eh_frame data from crtbeginT.o instead of the

[Bug tree-optimization/110769] ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1023

2023-07-22 Thread zhendong.su at inf dot ethz.ch via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110769 Zhendong Su changed: What|Removed |Added CC||zhendong.su at inf dot ethz.ch ---

[Bug middle-end/107737] seemly looking off code in gimplify_call_expr

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107737 --- Comment #3 from Andrew Pinski --- A C++ front-end does not set the call for deconstructor for the following testcase: ``` struct s{ ~s(); }; void f() { s{}; } ```

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org

[PATCH 2/2] AARCH64: Turn off unwind tables for crtbeginT.o

2023-07-22 Thread Andrew Pinski via Gcc-patches
The problem -fasynchronous-unwind-tables is on by default for aarch64 We need turn it off for crt*.o because it would make __EH_FRAME_BEGIN__ point to .eh_frame data from crtbeginT.o instead of the user-defined object during static linking. This turns it off. OK? Bootstrapped and tested on

[PATCH 1/2] Fix PR 110066: crash with -pg -static on riscv

2023-07-22 Thread Andrew Pinski via Gcc-patches
The problem -fasynchronous-unwind-tables is on by default for riscv linux We need turn it off for crt*.o because it would make __EH_FRAME_BEGIN__ point to .eh_frame data from crtbeginT.o instead of the user-defined object during static linking. This turns it off. OK? libgcc/ChangeLog:

[Bug middle-end/107737] seemly looking off code in gimplify_call_expr

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107737 --- Comment #2 from Andrew Pinski --- So far gimplify_vla_decl does not set the location on the call expression it creates. It should be set to the same as the decl source location. Testing that ...

[Bug tree-optimization/100864] (a&!b) | b is not opimized to a | b for comparisons

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100864 Andrew Pinski changed: What|Removed |Added URL||https://gcc.gnu.org/piperma

[PATCH] Fix 100864: `(a&!b) | b` is not opimized to `a | b` for comparisons

2023-07-22 Thread Andrew Pinski via Gcc-patches
This adds a special case of the `(a&~b) | b` pattern where `b` and `~b` are comparisons. OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions. gcc/ChangeLog: PR tree-optimization/100864 * match.pd ((~x & y) | x -> x | y): Add comparison variant.

gcc-13-20230722 is now available

2023-07-22 Thread GCC Administrator via Gcc
Snapshot gcc-13-20230722 is now available on https://gcc.gnu.org/pub/gcc/snapshots/13-20230722/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 13 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

[Committed] RISC-V: optim const DF +0.0 store to mem [PR/110748]

2023-07-22 Thread Vineet Gupta
Fixes: ef85d150b5963 ("RISC-V: Enable TARGET_SUPPORTS_WIDE_INT") DF +0.0 is bitwise all zeros so int x0 store to mem can be used to optimize it. void zd(double *) { *d = 0.0; } currently: | fmv.d.x fa5,zero | fsd fa5,0(a0) | ret With patch | sd zero,0(a0) | ret The fix updates

[Bug target/110748] RISC-V: optimize store of DF 0.0

2023-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110748 --- Comment #14 from CVS Commits --- The master branch has been updated by Vineet Gupta : https://gcc.gnu.org/g:ecfa870ff29d979bd2c3d411643b551f2b6915b0 commit r14-2731-gecfa870ff29d979bd2c3d411643b551f2b6915b0 Author: Vineet Gupta Date:

Re: [PATCH v2] RISC-V: optim const DF +0.0 store to mem [PR/110748]

2023-07-22 Thread Vineet Gupta
On 7/21/23 23:05, Jeff Law wrote: On 7/21/23 12:30, Vineet Gupta wrote: Fixes: ef85d150b5963 ("RISC-V: Enable TARGET_SUPPORTS_WIDE_INT") (gcc-13 regression) DF +0.0 is bitwise all zeros so int x0 store to mem can be used to optimize it. void zd(double *) { *d = 0.0; } currently: |

Re: Please stop blocking xstyle/stylish

2023-07-22 Thread Arsen Arsenović via Gcc
zxuiji via Gcc writes: > Your site is far too bright and is absolutely painful to the eyes, I > have a simple invert style that I expected to work on all sites and I > found your site is undertaking the vile act of blocking user styles. I > expect that sort of rotten design from microsoft &

[Bug rtl-optimization/110587] [14 regression] 96% pr28071.c compile time regression since r14-2337-g37a231cc7594d1

2023-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110587 --- Comment #13 from CVS Commits --- The master branch has been updated by Roger Sayle : https://gcc.gnu.org/g:8125b12f846b41f26e58c0fe3b218d654f65d1c8 commit r14-2730-g8125b12f846b41f26e58c0fe3b218d654f65d1c8 Author: Roger Sayle Date: Sat

[Bug target/110533] [x86-64] naked with -O0 and register-passed struct/int128 clobbers parameters/callee-saved regs

2023-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110533 --- Comment #5 from CVS Commits --- The master branch has been updated by Roger Sayle : https://gcc.gnu.org/g:8125b12f846b41f26e58c0fe3b218d654f65d1c8 commit r14-2730-g8125b12f846b41f26e58c0fe3b218d654f65d1c8 Author: Roger Sayle Date: Sat

[Bug target/110778] [14 Regression] Alpha targets broken since r14-2587-gd8105b10fff951 (undefined reference to extended_count)

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110778 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/110778] [14 Regression] Alpha targets broken since r14-2587-gd8105b10fff951 (undefined reference to extended_count)

2023-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110778 --- Comment #2 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:659d856e1d424ea8ef634844a7bd08b86ec7344b commit r14-2729-g659d856e1d424ea8ef634844a7bd08b86ec7344b Author: Andrew Pinski Date:

[PATCH] Fix alpha building

2023-07-22 Thread Andrew Pinski via Gcc-patches
The problem is after r14-2587-gd8105b10fff951, the definition of extended_count now takes a bool as its last argument but we only have a declaration for the version which takes an int as the last argument. This fixes the problem by changing the declaration to be a bool too. Committed as obvious

[Bug target/110778] [14 Regression] Alpha targets broken since r14-2587-gd8105b10fff951 (undefined reference to extended_count)

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110778 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Summary|Alpha

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #20 from Andrew Pinski --- (In reply to Andreas Schwab from comment #19) > Probably also needed for aarch64. Testing that and will submit both patches after that finishes.

[Bug target/110778] New: Alpha targets broken since r14-2587-gd8105b10fff951 (undefined reference to extended_count)

2023-07-22 Thread jamborm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110778 Bug ID: 110778 Summary: Alpha targets broken since r14-2587-gd8105b10fff951 (undefined reference to extended_count) Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug tree-optimization/110755] [13/14 Regression] Wrong optimization of fabs on ppc64el at -O1

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110755 --- Comment #7 from Aurelien Jarno --- (In reply to Jakub Jelinek from comment #6) > Created attachment 55594 [details] > gcc14-pr110755.patch > > Untested patch. Thanks for the patch, I confirm it works as expected, now the result is a

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 David Binderman changed: What|Removed |Added CC||rguenth at gcc dot gnu.org ---

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 --- Comment #4 from David Binderman --- Current range seems to be g:23ad5ed7432bea7c to g:85a4e4f93ff251f2. Trying g:b6b72562d116bd0a

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 --- Comment #3 from David Binderman --- Attempting bisection. Trying g:85a4e4f93ff251f2

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 --- Comment #2 from David Binderman --- Created attachment 55615 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55615=edit C source code Original pre-reduction source code.

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 --- Comment #1 from Andrew Pinski --- Is this reduced from some other code? Because the testcase here depends on an uninitialized variable.

[Bug tree-optimization/110777] [14 Regression] ice: SSA corruption

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 Andrew Pinski changed: What|Removed |Added Summary|ice: SSA corruption |[14 Regression] ice: SSA

[Bug c/110777] New: ice: SSA corruption

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110777 Bug ID: 110777 Summary: ice: SSA corruption Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee:

[Bug analyzer/110433] ASAN reports mismatching new/delete when compiling analyzer testcases

2023-07-22 Thread jamborm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110433 --- Comment #5 from Martin Jambor --- Indeed, the error is no longer reported. Thanks.

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #19 from Andreas Schwab --- Probably also needed for aarch64.

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #18 from Aurelien Jarno --- (In reply to Andreas Schwab from comment #17) > I don't think you need -fno-omit-frame-pointer. I confirm that CRTSTUFF_T_CFLAGS += -fno-asynchronous-unwind-tables -fno-unwind-tables is enough to fix the

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #17 from Andreas Schwab --- I don't think you need -fno-omit-frame-pointer.

Re: [x86 PATCH] Don't use insvti_{high, low}part with -O0 (for compile-time).

2023-07-22 Thread Uros Bizjak via Gcc-patches
On Sat, Jul 22, 2023 at 4:17 PM Roger Sayle wrote: > > > This patch attempts to help with PR rtl-optimization/110587, a regression > of -O0 compile time for the pathological pr28071.c. My recent patch helps > a bit, but hasn't returned -O0 compile-time to where it was before my >

Re: [x86 PATCH] Use QImode for offsets in zero_extract/sign_extract in i386.md

2023-07-22 Thread Uros Bizjak via Gcc-patches
On Sat, Jul 22, 2023 at 5:37 PM Roger Sayle wrote: > > > As suggested by Uros, this patch changes the ZERO_EXTRACTs and SIGN_EXTRACTs > in i386.md to consistently use QImode for bit offsets (i.e. third and fourth > operands), matching the use of QImode for bit counts in shifts and rotates. > >

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #16 from Andrew Pinski --- (In reply to Aurelien Jarno from comment #15) > (In reply to Andrew Pinski from comment #14) > > Created attachment 55614 [details] > > patch for someone to test out > > > > The problem is the similar

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #15 from Aurelien Jarno --- (In reply to Andrew Pinski from comment #14) > Created attachment 55614 [details] > patch for someone to test out > > The problem is the similar across many targets so I basically copied what > was done

[committed] testsuite: Limit bb-slp-pr95839-v8.c to 64-bit vector targets

2023-07-22 Thread Maciej W. Rozycki
Only run bb-slp-pr95839-v8.c with targets that support vectors of 64 bits, removing regressions with 32-bit x86 targets: FAIL: gcc.dg/vect/bb-slp-pr95839-v8.c scan-tree-dump slp2 "optimized: basic block" FAIL: gcc.dg/vect/bb-slp-pr95839-v8.c -flto -ffat-lto-objects scan-tree-dump slp2

[Bug fortran/110677] UBSAN error: load of value 1818451807, which is not a valid value for type 'expr_t' when compiling pr49213.f90

2023-07-22 Thread jamborm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110677 Martin Jambor changed: What|Removed |Added CC||pault at gcc dot gnu.org --- Comment

[PATCH] Replace lra-spill.cc's return_regno_p with return_reg_p.

2023-07-22 Thread Roger Sayle
This patch is my attempt to address the compile-time hog issue in PR rtl-optimization/110587. Richard Biener's analysis shows that compilation of pr28071.c with -O0 currently spends ~70% in timer "LRA non-specific" due to return_regno_p failing to filter a large number of calls to

[Bug tree-optimization/110766] [14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: in gimple_phi_arg_def_from_edge, at gimple.h:4699

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110766 --- Comment #3 from David Binderman --- Reduced C++ code seems to be: template struct _Base_bitset { unsigned long _M_w[_Nw]; unsigned long &_M_getword() { return _M_w[0]; } }; struct bitset : _Base_bitset<0> { int

[Bug target/110776] [14 Regression] powerpc-darwin bootstrap broken after r14-2490 with ICE rs6000.cc:5069 building libgfortran

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110776 Andrew Pinski changed: What|Removed |Added Keywords||build Target Milestone|---

Re: [PATCH 4/9] vect: Adjust vectorizable_load costing on VMAT_ELEMENTWISE and VMAT_STRIDED_SLP

2023-07-22 Thread Iain Sandoe
Hi Kewen, This patch breaks bootstrap on powerpc-darwin (which has Altivec, but not VSX) while building libgfortran. > On 3 Jul 2023, at 04:19, Kewen.Lin via Gcc-patches > wrote: Please see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110776 thanks Iain

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #14 from Andrew Pinski --- Created attachment 55614 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55614=edit patch for someone to test out The problem is the similar across many targets so I basically copied what was done

[committed] Fix length computation bug in bfin port

2023-07-22 Thread Jeff Law via Gcc-patches
The tester seemed to occasionally ping-pong a compilation failure on the builtin-bitops-1.c test. I long suspected it was something like length computations. I finally got a few minutes to dig into it, and sure enough the blackfin port was claiming the "ones" operation was 2 bytes when it is

[Bug target/110066] [13/14 Regression] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Summary|[RISC-V] Segment

[Bug target/110772] strange code generated for bit-field access

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #8 from Roland Illig --- When I compile the attached code with "ARM GCC 10.5.0" and "-O2 -fPIE -ftrapv" on godbolt.org, the generated code is correct (you can search for "#327" in the output and then go back one branch). The code

[Bug target/110776] [14 Regression] powerpc-darwin bootstrap broken after r14-2490 with ICE rs6000.cc:5069 building libgfortran

2023-07-22 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110776 --- Comment #1 from Iain Sandoe --- Created attachment 55613 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55613=edit preprocessed (not reduced, but the function is not large)

[Bug target/110741] vec_ternarylogic intrinsic generates incorrect code on POWER10 target when compiled with GCC

2023-07-22 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110741 --- Comment #3 from Peter Bergner --- (In reply to Kewen Lin from comment #2) > It exposed one issue on xxeval output vsx operands' format, can be fixed > with: > > diff --git a/gcc/config/rs6000/vsx.md b/gcc/config/rs6000/vsx.md > index

[Bug target/110776] New: [14 Regression] powerpc-darwin bootstrap broken after r14-2490 with ICE rs6000.cc:5069 building libgfortran

2023-07-22 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110776 Bug ID: 110776 Summary: [14 Regression] powerpc-darwin bootstrap broken after r14-2490 with ICE rs6000.cc:5069 building libgfortran Product: gcc Version: 14.0 Status:

[x86 PATCH] Use QImode for offsets in zero_extract/sign_extract in i386.md

2023-07-22 Thread Roger Sayle
As suggested by Uros, this patch changes the ZERO_EXTRACTs and SIGN_EXTRACTs in i386.md to consistently use QImode for bit offsets (i.e. third and fourth operands), matching the use of QImode for bit counts in shifts and rotates. There's no change in functionality, and the new patterns simply

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #12 from Aurelien Jarno --- Backtrace with debug symbols in libgcc_eh.a: Program received signal SIGSEGV, Segmentation fault. classify_object_over_fdes (ob=0xe2da0 , this_fde=0x1000530e6, range=0x3ff310) at

[Bug target/110772] strange code generated for bit-field access

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #7 from Roland Illig --- Created attachment 55612 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55612=edit Preprocessed source from comment 5

[Bug target/110772] strange code generated for bit-field access

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 Roland Illig changed: What|Removed |Added Attachment #55598|0 |1 is obsolete|

[Bug target/110772] strange code generated for bit-field access

2023-07-22 Thread roland.illig at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110772 --- Comment #5 from Roland Illig --- Sorry for the confusing description. Let me try again. NetBSD lint includes a yacc parser for C code. This parser contains the rules 'block_item_list' and 'block_item':

[PATCH v5 3/3] c++: Track lifetimes in constant evaluation [PR70331,PR96630,PR98675]

2023-07-22 Thread Nathaniel Shead via Gcc-patches
This adds rudimentary lifetime tracking in C++ constexpr contexts, allowing the compiler to report errors with using values after their backing has gone out of scope. We don't yet handle other ways of accessing values outside their lifetime (e.g. following explicit destructor calls). PR

[PATCH v5 2/3] c++: Prevent dangling pointers from becoming nullptr in constexpr [PR110619]

2023-07-22 Thread Nathaniel Shead via Gcc-patches
Currently, when typeck discovers that a return statement will refer to a local variable it rewrites to return a null pointer. This causes the error messages for using the return value in a constant expression to be unhelpful, especially for reference return values, and is also a visible change to

[PATCH v5 1/3] c++: Improve location information in constant evaluation

2023-07-22 Thread Nathaniel Shead via Gcc-patches
This patch updates 'input_location' during constant evaluation to ensure that errors in subexpressions that lack location information still provide accurate diagnostics. By itself this change causes some small regressions in diagnostic quality for circumstances where errors used 'input_location'

[PATCH v5 0/3] c++: Track lifetimes in constant evaluation [PR70331, ...]

2023-07-22 Thread Nathaniel Shead via Gcc-patches
This is an update of the patch series at https://gcc.gnu.org/pipermail/gcc-patches/2023-July/625050.html Changes since v4: - Reordered patches to be more independent from each other (they don't need to keep updating the new tests) - Removed workaround for better locations in

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #11 from Aurelien Jarno --- I have bisected the issue, and I found it has been introduced by the following commit: commit 3cd08f7168c196d7a481b9ed9f4289fd1f14eea8 Author: Andreas Schwab Date: Wed Jan 25 12:00:09 2023 +0100

Re: [WIP RFC] analyzer: Add optional trim of the analyzer diagnostics going too deep [PR110543]

2023-07-22 Thread Prathamesh Kulkarni via Gcc-patches
On Fri, 21 Jul 2023 at 21:05, Benjamin Priour via Gcc-patches wrote: > > Hi, > > Upon David's request I've joined the in progress patch to the below email. > I hope it makes more sense now. > > Best, > Benjamin. > > -- Forwarded message - > From: Benjamin Priour > Date: Tue, Jul

[Bug tree-optimization/110766] [14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: in gimple_phi_arg_def_from_edge, at gimple.h:4699

2023-07-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110766 David Binderman changed: What|Removed |Added CC||dcb314 at hotmail dot com ---

[x86 PATCH] Don't use insvti_{high, low}part with -O0 (for compile-time).

2023-07-22 Thread Roger Sayle
This patch attempts to help with PR rtl-optimization/110587, a regression of -O0 compile time for the pathological pr28071.c. My recent patch helps a bit, but hasn't returned -O0 compile-time to where it was before my ix86_expand_move changes. The obvious solution/workaround is to guard these

Re: [PATCH v3 1/3] c++, libstdc++: Implement __is_arithmetic built-in trait

2023-07-22 Thread François Dumont via Gcc-patches
On 18/07/2023 08:27, Ken Matsui via Libstdc++ wrote: This patch implements built-in trait for std::is_arithmetic. gcc/cp/ChangeLog: * cp-trait.def: Define __is_arithmetic. * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_ARITHMETIC. * semantics.cc

Re: [PATCH v2 3/3] libstdc++: Optimize is_fundamental performance by __is_arithmetic built-in

2023-07-22 Thread François Dumont via Gcc-patches
It seems rather logical cause std::disjunction is supposed to avoid instantiations but in case of: std::disjunction, std::is_null_pointer<_Tp>> you'll avoid std::is_null_pointer instantiation only for 'void' type and at the price of instantiating std::disjunction so 2 instantiations at best

Re: [PATCH v2 2/3] libstdc++: Optimize is_arithmetic performance by __is_arithmetic built-in

2023-07-22 Thread François Dumont via Gcc-patches
On 17/07/2023 06:48, Ken Matsui wrote: On Sun, Jul 16, 2023 at 5:32 AM François Dumont wrote: On 15/07/2023 06:55, Ken Matsui via Libstdc++ wrote: This patch optimizes the performance of the is_arithmetic trait by dispatching to the new __is_arithmetic built-in trait.

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #10 from Aurelien Jarno --- (In reply to Aurelien Jarno from comment #9) > (In reply to Andrew Pinski from comment #5) > > Can you try reverting r13-923-g2d546ff69455f7deadab and try GCC 13 again? > > Yep, I'll do that, but it will

[Bug middle-end/110757] [14 Regression] 7% parest regression on zen3 -Ofast -march=native -flto between g:4dbb3af1efe55174 (2023-07-14 00:54) and g:a5088dc3f5ef73c8 (2023-07-17 03:24)

2023-07-22 Thread jamborm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110757 Martin Jambor changed: What|Removed |Added CC||lili.cui at intel dot com,

[Bug libgcc/110775] [12/13/14 Regression] abort define causing issues in tsystem.h

2023-07-22 Thread sebastian.huber--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110775 Sebastian Huber changed: What|Removed |Added CC||sebastian.huber@embedded-br

[Bug modula2/110174] Using illegal constraints for builtin return_address gives ICE

2023-07-22 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110174 Gaius Mulley changed: What|Removed |Added Last reconfirmed||2023-07-22 Ever confirmed|0

Re: [PATCH] LoongArch: Allow using --with-arch=native if host CPU is LoongArch

2023-07-22 Thread chenglulu
在 2023/7/20 下午9:28, Xi Ruoyao 写道: If the host triple and the target triple are different but the host is LoongArch, in some cases --with-arch=native can be useful. For example, if we are bootstrapping a loongarch64-linux-musl toolchain on a Glibc-based system and we don't intend to use the

[Bug modula2/110631] Bug in FIO.WriteCardinal

2023-07-22 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110631 Gaius Mulley changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug modula2/110631] Bug in FIO.WriteCardinal

2023-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110631 --- Comment #3 from CVS Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:73cc6ce1294ec35e9322b1bbc91009cfc76f732b commit r14-2725-g73cc6ce1294ec35e9322b1bbc91009cfc76f732b Author: Gaius Mulley Date:

[Bug libstdc++/109921] [13 Regression] c++17/floating_from_chars.cc: compile error: ‘from_chars_strtod’ was not declared in this scope

2023-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109921 --- Comment #12 from Jonathan Wakely --- Excellent, thanks for checking.

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #9 from Aurelien Jarno --- (In reply to Andrew Pinski from comment #5) > Can you try reverting r13-923-g2d546ff69455f7deadab and try GCC 13 again? Yep, I'll do that, but it will probably take some time to get the results. (In

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #8 from Aurelien Jarno --- Created attachment 55610 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55610=edit crtbeginT.o GCC 12 version

[Bug target/110066] [RISC-V] Segment fault if compiled with -static -pg

2023-07-22 Thread aurelien at aurel32 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110066 --- Comment #7 from Aurelien Jarno --- Created attachment 55609 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55609=edit crtbeginT.o GCC 12 version

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #15 from AlexK --- I have attached all patches I have made to several Makefile.in in different folders (I created them with `diff` tool) after that I made building directory: installdir=/tools/gcc-12.2.0 install -v -d mybuild cd

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #14 from AlexK --- Created attachment 55608 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55608=edit applyed patch for gcc/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #13 from AlexK --- Created attachment 55607 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55607=edit applyed patch for libcpp/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #12 from AlexK --- Created attachment 55606 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55606=edit applyed patch for libbacktrace/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #11 from AlexK --- Created attachment 55605 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55605=edit applyed patch for libcody/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #10 from AlexK --- Created attachment 55604 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55604=edit applyed patch for libdecnumber/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #9 from AlexK --- Created attachment 55603 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55603=edit applyed patch for libiberty/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #8 from AlexK --- Created attachment 55602 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55602=edit applyed patch for libgcc/Makefile.in to make shared library

[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

2023-07-22 Thread alexei_sylver1 at mail dot ru via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684 --- Comment #7 from AlexK --- Created attachment 55601 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55601=edit applyed patch for Makefile.in to configure with --enable-shared and without --enable-static options

[Bug modula2/110631] Bug in FIO.WriteCardinal

2023-07-22 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110631 --- Comment #2 from Gaius Mulley --- Created attachment 55600 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55600=edit Proposed fix Here is a proposed fix - which will be applied (if/when) bootstrapping completes successfully.

[Bug tree-optimization/93116] match.pd uses convert/tree_nop_conversion_p instead of nop_convert

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93116 --- Comment #2 from Andrew Pinski --- So the biggest issue here is that if we use nop_convert here, we will need to check for vectors and use view_convert instead of convert in the resulting output for the patterns. like what is done for: /*

[Bug target/54904] Large mode constant live in a register not used to optimize smaller mode constants

2023-07-22 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54904 Andrew Pinski changed: What|Removed |Added Assignee|pinskia at gcc dot gnu.org |unassigned at gcc dot gnu.org

Re: [PATCH] match.pd: Implement missed optimization (x << c) >> c -> -(x & 1) [PR101955]

2023-07-22 Thread Jeff Law via Gcc-patches
On 7/21/23 11:27, Andrew Pinski via Gcc-patches wrote: On Fri, Jul 21, 2023 at 8:09 AM Drew Ross via Gcc-patches wrote: Simplifies (x << c) >> c where x is a signed integral type of width >= int and c = precision(type) - 1 into -(x & 1). Tested successfully on x86_64 and x86 targets.

[Bug libstdc++/109921] [13 Regression] c++17/floating_from_chars.cc: compile error: ‘from_chars_strtod’ was not declared in this scope

2023-07-22 Thread br015 at umbiko dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109921 --- Comment #11 from Andreas Ziegler --- Tested successfully cross-compiling for x86_64-buildroot-linux-uclibc w/o locale Regression tests successful for i586-buildroot-linux-uclibc w/o locale aarch64-buildroot-linux-musl w/ locale

Re: [PATCH v2] RISC-V: optim const DF +0.0 store to mem [PR/110748]

2023-07-22 Thread Jeff Law via Gcc-patches
On 7/21/23 12:30, Vineet Gupta wrote: Fixes: ef85d150b5963 ("RISC-V: Enable TARGET_SUPPORTS_WIDE_INT") (gcc-13 regression) DF +0.0 is bitwise all zeros so int x0 store to mem can be used to optimize it. void zd(double *) { *d = 0.0; } currently: | fmv.d.x fa5,zero | fsd fa5,0(a0) |

Re: [PATCH] RISC-V: optim const DF +0.0 store to mem [PR/110748]

2023-07-22 Thread Jeff Law via Gcc-patches
On 7/21/23 12:55, Vineet Gupta wrote: Apparently this is a regression in gcc-13, introduced by commit ef85d150b5963 ("RISC-V: Enable TARGET_SUPPORTS_WIDE_INT") and the fix thus is a partial revert of that change. Given that it can ICE, we should probably backport it to 13. FWIW ICE is

  1   2   >