[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 --- Comment #4 from Sam James --- Created attachment 56520 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56520&action=edit list_of_differing_files.txt

[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 Sam James changed: What|Removed |Added CC||law at gcc dot gnu.org --- Comment #5 from

[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 --- Comment #6 from Jeffrey A. Law --- Do we have assembly code around the faulting point (x/20i $pc) and a register dump (i r)? The biggest concern I'd have with f-m-o on the PA would be the implicit segment selection that happens on the base

[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 --- Comment #7 from dave.anglin at bell dot net --- On 2023-11-06 5:20 p.m., law at gcc dot gnu.org wrote: > The biggest concern I'd have with f-m-o on the PA would be the > implicit segment selection that happens on the base register -- but it w

[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 --- Comment #8 from Sam James --- (In reply to Jeffrey A. Law from comment #6) Program received signal SIGSEGV, Segmentation fault. 0x412083f0 in _PyST_GetSymbol (name=0xf9a34a00, ste=) at Python/symtable.c:396 396 PyObject *v = PyDict_

[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 --- Comment #9 from Sam James --- I think the key object is Python/compile.o, but not certain yet.

[Bug libbacktrace/111315] libstdc++ stacktrace testsuite failures with --enable-default-pie

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315 --- Comment #8 from CVS Commits --- The master branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:2b64e4a54042fb8f75f1c1429eb1c13afb9fa118 commit r14-5173-g2b64e4a54042fb8f75f1c1429eb1c13afb9fa118 Author: Ian Lance Taylor Dat

[Bug libbacktrace/112263] [C++23] std::stacktrace does not identify symbols in shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263 --- Comment #13 from CVS Commits --- The master branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:2b64e4a54042fb8f75f1c1429eb1c13afb9fa118 commit r14-5173-g2b64e4a54042fb8f75f1c1429eb1c13afb9fa118 Author: Ian Lance Taylor Da

[Bug libbacktrace/111315] libstdc++ stacktrace testsuite failures with --enable-default-pie

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315 --- Comment #9 from CVS Commits --- The releases/gcc-13 branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:8484e3479fe80aebdc4a2406473aef906055b4f8 commit r13-8006-g8484e3479fe80aebdc4a2406473aef906055b4f8 Author: Ian Lance Ta

[Bug libbacktrace/112263] [C++23] std::stacktrace does not identify symbols in shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263 --- Comment #14 from CVS Commits --- The releases/gcc-13 branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:8484e3479fe80aebdc4a2406473aef906055b4f8 commit r13-8006-g8484e3479fe80aebdc4a2406473aef906055b4f8 Author: Ian Lance T

[Bug libbacktrace/112263] [C++23] std::stacktrace does not identify symbols in shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263 --- Comment #15 from CVS Commits --- The releases/gcc-12 branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:56909c9d4842925749cd9e061ef4afa0501f85e9 commit r12-9961-g56909c9d4842925749cd9e061ef4afa0501f85e9 Author: Ian Lance T

[Bug libbacktrace/111315] libstdc++ stacktrace testsuite failures with --enable-default-pie

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315 --- Comment #10 from CVS Commits --- The releases/gcc-12 branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:56909c9d4842925749cd9e061ef4afa0501f85e9 commit r12-9961-g56909c9d4842925749cd9e061ef4afa0501f85e9 Author: Ian Lance T

[Bug libbacktrace/112263] [C++23] std::stacktrace does not identify symbols in shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263 Ian Lance Taylor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug rtl-optimization/112415] [14 regression] Python 3.11 miscompiled on HPPA with new RTL fold mem offset pass, since r14-4664-g04c9cf5c786b94

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415 --- Comment #10 from dave.anglin at bell dot net --- On 2023-11-06 5:49 p.m., sjames at gcc dot gnu.org wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x412083f0 in _PyST_GetSymbol (name=0xf9a34a00, ste=) at > Python/symtable.c:3

[Bug libbacktrace/112263] [C++23] std::stacktrace does not identify symbols in shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112263 --- Comment #17 from Jonathan Wakely --- Thanks, Ian!

[Bug middle-end/110015] openjpeg is slower when built with gcc13 compared to clang16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015 --- Comment #5 from Andrew Pinski --- After fixing PR 112324 (and a secondary patch to phiopt to do factor_out_conditional_operation for all phi nodes rather than just a single one) we still miss the abs detection: _34 = tmp_24 < 0; _55 = (

[Bug tree-optimization/112416] New: absu is not detected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112416 Bug ID: 112416 Summary: absu is not detected Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3

[Bug middle-end/110015] openjpeg is slower when built with gcc13 compared to clang16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015 Andrew Pinski changed: What|Removed |Added Depends on||112416 --- Comment #6 from Andrew Pinsk

[Bug middle-end/110015] openjpeg is slower when built with gcc13 compared to clang16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Severity|normal

[Bug testsuite/112340] [14 regression] assembler instruction counts off for gcc.target/powerpc/pr106550_1.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112340 Kewen Lin changed: What|Removed |Added Last reconfirmed||2023-11-07 Status|UNCONFIRMED

[Bug rtl-optimization/112417] New: expand_builtin_return shoud check alignment for the memory reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112417 Bug ID: 112417 Summary: expand_builtin_return shoud check alignment for the memory reference Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug target/111907] ICE: in curr_insn_transform, at lra-constraints.cc:4294 unable to generate reloads for: {*andnottf3} with -mavx512f -mno-evex512

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111907 --- Comment #6 from Haochen Jiang --- Proposed patch: https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635410.html

[Bug rtl-optimization/112417] expand_builtin_return shoud check alignment for the memory reference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112417 HaoChen Gui changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |guihaoc at gcc dot gnu.org

[Bug tree-optimization/112418] New: factor_out_conditional_operation could be done for more phis

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112418 Bug ID: 112418 Summary: factor_out_conditional_operation could be done for more phis Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimizati

[Bug tree-optimization/112418] factor_out_conditional_operation could be done for more phis

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112418 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2023-11-07 Status|UNCONFIRM

[Bug middle-end/110015] openjpeg is slower when built with gcc13 compared to clang16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015 Andrew Pinski changed: What|Removed |Added Depends on||112418 --- Comment #8 from Andrew Pinsk

[Bug middle-end/110015] openjpeg is slower when built with gcc13 compared to clang16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015 --- Comment #9 from Andrew Pinski --- I should note that PR 112416 is not needed to vectorize the loop, though it would improve code.

[Bug tree-optimization/112402] [11/12/13/14 Regression] Path splitting causes if-conversion miss

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112402 --- Comment #2 from Andrew Pinski --- The orginal threads about patch splitting: https://gcc.gnu.org/legacy-ml/gcc/2015-03/msg00057.html https://gcc.gnu.org/pipermail/gcc/2015-May/217495.html > or axe path splitting or move it to RTL Jeff had a

[Bug middle-end/112382] `(a&b) != a` where a is known to have one known bit set is not optimized to ((~b&a)>>shift) & 1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112382 --- Comment #2 from Andrew Pinski --- (In reply to Richard Biener from comment #1) > Note ((~b&a)>>shift) & 1 is two more GIMPLE ops than (a&b) != a so I'd > expect the reverse transform on GIMPLE and maybe target specific expansion > tweaks (or

[Bug tree-optimization/112419] New: [14 Regression] gcc.dg/Wnonnull-4.c excess error for 32-bit targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112419 Bug ID: 112419 Summary: [14 Regression] gcc.dg/Wnonnull-4.c excess error for 32-bit targets Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: diagnostic

[Bug tree-optimization/112419] [14 Regression] gcc.dg/Wnonnull-4.c excess error for 32-bit targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112419 uecker at gcc dot gnu.org changed: What|Removed |Added Ever confirmed|0 |1 See Also|

[Bug tree-optimization/105558] simple 8-bit integer calculation fails with -O3 / march=core-avx2 on some gfortran 8/9/10 versions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105558 --- Comment #8 from Thomas Koenig --- (In reply to Andrew Pinski from comment #6) > Would be interesting to find what patch broke this and what patch fixed the > -mtune=generic case. It is not easy bisecting with old compilers - compilation iss

[Bug target/112399] RISC-V: Missed AVL propagation for complicate reduction case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112399 --- Comment #1 from CVS Commits --- The master branch has been updated by Pan Li : https://gcc.gnu.org/g:f1e084c6c3ef1d1233e35823dacfdf9cee722430 commit r14-5179-gf1e084c6c3ef1d1233e35823dacfdf9cee722430 Author: Juzhe-Zhong Date: Mon Nov 6

[Bug target/112399] RISC-V: Missed AVL propagation for complicate reduction case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112399 JuzheZhong changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/112420] New: Unexpected vectorization for RISC-V

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112420 Bug ID: 112420 Summary: Unexpected vectorization for RISC-V Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c++/112421] New: GCC emits warning potential null dereference

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112421 Bug ID: 112421 Summary: GCC emits warning potential null dereference Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

<    1   2