[PATCH] match.pd: Fix ICE on BIT_INSERT_EXPR of BIT_FIELD_REF folding [PR113967]

Hi! The following testcase ICEs, because BIT_FIELD_REF's position is not multiple of the vector element's bit size and the code uses exact_div to divide those 2 values. For BIT_INSERT_EXPR, the tree-cfg.cc verification verifies the position is a multiple of the inserted bit size when inserting

[Bug tree-optimization/113962] [14 Regression] ICE: in exact_div, at poly-int.h:2156 with -O -mavx512f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113962 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[PATCH] c-family, c++: Fix up handling of types which may have padding in __atomic_{compare_}exchange

On Fri, Feb 16, 2024 at 01:51:54PM +, Jonathan Wakely wrote: > Ah, although __atomic_compare_exchange only takes pointers, the > compiler replaces that with a call to __atomic_compare_exchange_n > which takes the newval by value, which presumably uses an 80-bit FP > register and so the padding

[Bug tree-optimization/113962] New: [14 Regression] ICE: in exact_div, at poly-int.h:2156 with -O -mavx512f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113962 Bug ID: 113962 Summary: [14 Regression] ICE: in exact_div, at poly-int.h:2156 with -O -mavx512f Product: gcc Version: 14.0 Status: WAITING Keywords:

[Bug target/113960] std::map with std::vector as input overwrites itself with c++20, on s390x platform

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113960 Richard Biener changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug middle-end/113959] Optimize `__builtin_isnan(x) || __builtin_isinf(x)` to `__builtin_isfinite(x)`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113959 Richard Biener changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

Re: [PATCH v2] RISC-V: Suppress the vsetvl fusion for conflict successors

Ping this patch which is simple fix on VSETVL PASS. Ok for trunk ? juzhe.zh...@rivai.ai From: Juzhe-Zhong Date: 2024-02-01 17:02 To: gcc-patches CC: kito.cheng; kito.cheng; jeffreyalaw; rdapp.gcc; Juzhe-Zhong Subject: [PATCH v2] RISC-V: Suppress the vsetvl fusion for conflict successors

Re: [PATCH v1] Internal-fn: Add new internal function SAT_ADDU

On Sat, Feb 17, 2024 at 11:30 AM wrote: > > From: Pan Li > > This patch would like to add the middle-end presentation for the > unsigned saturation add. Aka set the result of add to the max > when overflow. It will take the pattern similar as below. > > SAT_ADDU (x, y) => (x + y) |

[Bug c++/113987] [12/13/14 Regression] Binding a reference to an uninitialized data member should not cause -Wuninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987 Jakub Jelinek changed: What|Removed |Added Priority|P3 |P2 CC|

Re: [PATCH][_GLIBCXX_DEBUG] Fix std::__niter_base behavior

On 2/17/24 15:14, François Dumont wrote: Thanks for the link, tested and committed. I assume this is the cause for the below failure now, $ cat test.cc #include #include void f(std::vector , void const * p) { std::erase(v, p); } $ ~/gcc/inst/bin/g++ -std=c++20 -D_GLIBCXX_DEBUG

[Bug c++/113987] [12/13/14 Regression] Binding a reference to an uninitialized data member should not cause -Wuninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987 --- Comment #4 from Andrew Pinski --- (In reply to Fangrui Song from comment #1) > BTW, > https://github.com/llvm/llvm-project/blob/main/clang/test/SemaCXX/ > uninitialized.cpp has many member initializer list examples And

[Bug c++/113987] [12/13/14 Regression] Binding a reference to an uninitialized data member should not cause -Wuninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987 --- Comment #3 from Andrew Pinski --- Most likely started with r12-5391-g0790c8aacdfb4f .

[Bug c++/113987] [12/13/14 Regression] Binding a reference to an uninitialized data member should not cause -Wuninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.4 Known to fail|

[Bug target/113986] [14 regression] Build failure on aarch64-linux-musl (error: 'export_load_16' aliased to undefined symbol 'libat_load_16')

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986 Andrew Pinski changed: What|Removed |Added CC||wilco at gcc dot gnu.org

[Bug middle-end/113987] Binding a reference to an uninitialized data member should not cause -Wuninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987 --- Comment #1 from Fangrui Song --- BTW, https://github.com/llvm/llvm-project/blob/main/clang/test/SemaCXX/uninitialized.cpp has many member initializer list examples

[Bug middle-end/113987] New: Binding a reference to an uninitialized data member should not cause -Wuninitialized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987 Bug ID: 113987 Summary: Binding a reference to an uninitialized data member should not cause -Wuninitialized Product: gcc Version: unknown Status: UNCONFIRMED

[Bug target/113986] [14 regression] Build failure on aarch64-linux-musl (error: 'export_load_16' aliased to undefined symbol 'libat_load_16')

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986 Andrew Pinski changed: What|Removed |Added Keywords||build Target Milestone|---

[PATCH] Fix testcase for platform without gnu/stubs-x32.h

target maybe_x32 doesn't check if platform has gnu/stubs-x32.h, but it's included by stdint.h in the testcase. Adjust testcase: remove stdint.h, use 'typedef long long int64_t' instead. Commit as an obvious patch. gcc/testsuite/ChangeLog: PR target/113711 *

[Bug target/113986] New: [14 regression] Build failure on aarch64-linux-musl (error: 'export_load_16' aliased to undefined symbol 'libat_load_16')

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986 Bug ID: 113986 Summary: [14 regression] Build failure on aarch64-linux-musl (error: 'export_load_16' aliased to undefined symbol 'libat_load_16') Product: gcc

[Bug middle-end/113985] expansion of `*struct = call();` could be improved

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113985 Andrew Pinski changed: What|Removed |Added Status|RESOLVED|NEW Keywords|

[Bug rtl-optimization/113985] redundant copy of return values at O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113985 Xi Ruoyao changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug rtl-optimization/113985] New: redundant copy of return values at O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113985 Bug ID: 113985 Summary: redundant copy of return values at O0 Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/109358] Wrong formatting with T-descriptor during stream output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109358 --- Comment #16 from Jerry DeLisle --- I think I was not being very clear when I opened pr113897. nX descriptors are very similar to TR code and I meeantt to take care of those in the 113897. The reason for the separate PR is that the problem

RE: [PATCH V4 4/5] RISC-V: Quick and simple fixes to testcases that break due to reordering

For calling-convention-*.c, LGTM but one nit about change log. Take **Update** here may make others not easy to learn what you did about the file. You can say similar to "Rearrange and adjust the asm-checker times" or likewise. Of course, you can refine the changelog when commit. > *

[Bug middle-end/113984] -Wfree-nonheap-object false positive with VLA parameter that has a size which is not a simple decl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984 Andrew Pinski changed: What|Removed |Added Summary|-Wfree-nonheap-object false |-Wfree-nonheap-object false

[Bug middle-end/113984] -Wfree-nonheap-object false positive with VLA parameter that is a derefenced

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug c/113984] -Wfree-nonheap-object false positive with VLA parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984 --- Comment #1 from Alejandro Colomar --- With -O3, the warning also vanishes, as the function is probably inlined, and there's no VLA parameter any more. alx@debian:~/tmp$ gcc-14 -Wall -O3 nonheap.c alx@debian:~/tmp$ gcc-13 -Wall -O3

[Bug c/113984] New: -Wfree-nonheap-object false positive with VLA parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984 Bug ID: 113984 Summary: -Wfree-nonheap-object false positive with VLA parameter Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH] m68k: restore bootstrap

On Sun, 2024-02-18 at 08:42 -0700, Jeff Law wrote: > > On 2/18/24 02:18, Mikael Pettersson wrote: > > m68k fails to bootstrap since -ffold-mem-offsets was introduced, > > in what looks like wrong-code during stage2. > > > > To restore bootstrap this disables -ffold-mem-offsets on m68k. > > It's

Re: CI for "Option handling: add documentation URLs"

Hi David, On Thu, Jan 04, 2024 at 09:57:09AM -0500, David Malcolm wrote: > I've pushed the .opt.urls patch kit to gcc trunk [1], so hopefully the > CI check you wrote can go live now. And then I was on vacation myself and forgot. I am sorry. So, I did try the regenerate-opt-urls locally, and it

gcc-14-20240218 is now available

Snapshot gcc-14-20240218 is now available on https://gcc.gnu.org/pub/gcc/snapshots/14-20240218/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 14 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

[Bug analyzer/113983] [14 Regression] ICE: tree check: expected integer_cst, have vector_cst in maybe_undo_optimize_bit_field_compare, at analyzer/region-model-manager.cc:606 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113983 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-02-18 CC|

[Bug middle-end/113982] Poor codegen for 64-bit add with carry widening functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug analyzer/113983] [14 Regression] ICE: tree check: expected integer_cst, have vector_cst in maybe_undo_optimize_bit_field_compare, at analyzer/region-model-manager.cc:606 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113983 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0 CC|

[Bug analyzer/113983] New: [14 Regression] ICE: tree check: expected integer_cst, have vector_cst in maybe_undo_optimize_bit_field_compare, at analyzer/region-model-manager.cc:606 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113983 Bug ID: 113983 Summary: [14 Regression] ICE: tree check: expected integer_cst, have vector_cst in maybe_undo_optimize_bit_field_compare, at

[Bug middle-end/113982] Poor codegen for 64-bit add with carry widening functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982 --- Comment #2 from Andrew Pinski --- Note some of this is due to return register issues. If we instead do stores: ``` add_wide_1(unsigned long long, unsigned long long, add_result*): mov rax, rdi lea rcx, [rdi+rsi]

[Bug middle-end/113982] Poor codegen for 64-bit add with carry widening functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982 Andrew Pinski changed: What|Removed |Added Component|target |middle-end Last reconfirmed|

[Bug c++/113982] New: Poor codegen for 64-bit add with carry widening functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982 Bug ID: 113982 Summary: Poor codegen for 64-bit add with carry widening functions Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug c++/113976] [11/12/13/14 Regression] explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss since r8-2857-g2ec399d8a6c9c2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[Bug c++/86761] Code corruption with missing pointer return

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86761 Andrew Pinski changed: What|Removed |Added CC||Simon.Richter at hogyros dot de ---

[Bug target/113981] risc-v: non-void C++ function with no return statement has no ret

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

[Bug target/113980] risc-v: unnecessary sign-extend after lw with volatile, and more

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113980 --- Comment #1 from Andrew Pinski --- Basically GCC does not optimize around a volatile memory load/stores which causes artifacts like this.

[Bug target/113981] New: risc-v: non-void C++ function with no return statement has no ret

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113981 Bug ID: 113981 Summary: risc-v: non-void C++ function with no return statement has no ret Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug target/113980] New: risc-v: unnecessary sign-extend after lw, and more

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113980 Bug ID: 113980 Summary: risc-v: unnecessary sign-extend after lw, and more Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/113976] [11/12/13/14 Regression] explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss since r8-2857-g2ec399d8a6c9c2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976 --- Comment #4 from Andrew Pinski --- (In reply to Jeffrey A. Law from comment #3) > What does the standard say about changing const objects? It says it is undefined. Note there is no changing const object in this code; just the const variable

[Bug c++/113976] [11/12/13/14 Regression] explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss since r8-2857-g2ec399d8a6c9c2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976 --- Comment #3 from Jeffrey A. Law --- What does the standard say about changing const objects?

[r14-9028 Regression] FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for errors, line 3350) on Linux/x86_64

On Linux/x86_64, 7f3d900684ad989164114f25eb46a33871c6533d is the first bad commit commit 7f3d900684ad989164114f25eb46a33871c6533d Author: Jonathan Wakely Date: Wed Feb 7 11:31:10 2024 + libstdc++: Fix FAIL: 26_numerics/random/pr60037-neg.cc [PR113931] caused FAIL:

[r14-8925 Regression] FAIL: gcc.dg/torture/pr56689.c -O3 -g (test for excess errors) on Linux/x86_64

On Linux/x86_64, 1e3f78dbb328a2f2db8def241372cb947d9cb7eb is the first bad commit commit 1e3f78dbb328a2f2db8def241372cb947d9cb7eb Author: Richard Biener Date: Mon Feb 12 10:40:42 2024 +0100 tree-optimization/113863 - elide degenerate virtual PHIs when moving ee stores caused FAIL:

[r14-8998 Regression] FAIL: 26_numerics/random/pr60037-neg.cc -std=gnu++17 (test for excess errors) on Linux/x86_64

On Linux/x86_64, c9ce332b557bb95987d038d98ea929cdfd1eae1d is the first bad commit commit c9ce332b557bb95987d038d98ea929cdfd1eae1d Author: Jonathan Wakely Date: Wed Feb 7 11:31:10 2024 + libstdc++: Use 128-bit arithmetic for std::linear_congruential_engine [PR87744] caused FAIL:

[Bug target/113971] [14 Regression] failure to build on arm64 musl (#error "Unsupported AArch64 platform for heap trampolines")

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113971 Iain Sandoe changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org

[PATCH] libstdc++, Darwin: Handle a linker warning [PR112397].

Tested on i686-darwin9, x86_64-darwin14,17,19,21,23, x86_64-linux, aarch64-linux-gnu, OK for trunk? eventual back-ports? thanks Iain --- 8< --- Darwin's linker warns when we make a direct branch to code that is in a weak definition (citing that if a different implementation of the weak function

[PATCH] x86-64: Check R_X86_64_CODE_6_GOTTPOFF support

If assembler and linker supports add %reg1, name@gottpoff(%rip), %reg2 with R_X86_64_CODE_6_GOTTPOFF, we can generate it instead of mov name@gottpoff(%rip), %reg2 add %reg1, %reg2 gcc/ * configure.ac (HAVE_AS_R_X86_64_CODE_6_GOTTPOFF): Defined as 1 if R_X86_64_CODE_6_GOTTPOFF

Re: [PATCH] m68k: restore bootstrap

On 2/18/24 02:18, Mikael Pettersson wrote: m68k fails to bootstrap since -ffold-mem-offsets was introduced, in what looks like wrong-code during stage2. To restore bootstrap this disables -ffold-mem-offsets on m68k. It's not ideal, but better than keeping bootstraps broken until the root

[Bug target/113912] push2/pop2 generated when stack isn't aligned to 16 bytes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113912 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/113912] push2/pop2 generated when stack isn't aligned to 16 bytes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113912 --- Comment #2 from GCC Commits --- The master branch has been updated by H.J. Lu : https://gcc.gnu.org/g:853eb57759967335a7ea872e6a0721034db6fabd commit r14-9058-g853eb57759967335a7ea872e6a0721034db6fabd Author: H.J. Lu Date: Tue Feb 13

[Bug ada/113979] New: Allocation of 2D array fails when Dynamic Predicate applied to type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113979 Bug ID: 113979 Summary: Allocation of 2D array fails when Dynamic Predicate applied to type Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/113974] Attribute common ignored

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113974 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[patch,avr,applied] Minor improvements to option and attribute documentation.

Applied this patch. Johann -- AVR: Improve documentation for -mmcu=. gcc/ * doc/invoke.texi (AVR Options) <-mmcu>: Remove "Atmel". Note on complete device support. AVR: Add examples for ISR macro to interrupt attribute doc. gcc/ * doc/extend.texi (AVR Function

[Bug middle-end/113974] Attribute common ignored

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113974 --- Comment #3 from Georg-Johann Lay --- Then the documentation should make that clear that with -fno-data-sections the object goes in COMM, but with -fdata-sections it does not and the attribute "common" is ignored. Better still, the compiler

[Bug c/44854] Improve diagnostic for missing member name or '; ' in a struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44854 peter0x44 at disroot dot org changed: What|Removed |Added CC||peter0x44 at disroot dot

[Bug target/113978] Misoptimize for long vector load operation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113978 --- Comment #8 from Jakub Jelinek --- (In reply to Jakub Jelinek from comment #7) > The psABI doesn't cover that. It only talks about __m128, __m256 and __m512 > types, and > as both compilers use the GNU vector_size attribute extension under

[Bug middle-end/112344] [14 Regression] Wrong code at -O2 on x86_64-pc-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112344 --- Comment #13 from GCC Commits --- The master branch has been updated by Dimitar Dimitrov : https://gcc.gnu.org/g:3796216bfa49b5ca288afe0760931a4c5b8ea346 commit r14-9055-g3796216bfa49b5ca288afe0760931a4c5b8ea346 Author: Dimitar Dimitrov

[Bug target/108640] ICE compiling busybox for m68k in change_address_1, at emit-rtl.cc:2283

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108640 --- Comment #10 from Anton Arnold --- I applied the patch to a gcc 13.2 buildroot toolchain for a coldfire cpu with ISA-A+ instruction set. Everything compiled fine and a linux 4.19 uclinux nommu build with buildroot and several custom packages

[Bug target/113915] [14 regression] glibc's _dl_find_object_update_1 miscompiled for armv7a since r14-4365-g0731889c026bfe

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113915 --- Comment #12 from Sam James --- (In reply to Andrew Pinski from comment #9) > This should work, I think: > [...] I'm going to apply this tonight for our arm builds downstream as we can't do any testing right now and there's a lot of bugs

[PATCH] m68k: restore bootstrap

m68k fails to bootstrap since -ffold-mem-offsets was introduced, in what looks like wrong-code during stage2. To restore bootstrap this disables -ffold-mem-offsets on m68k. It's not ideal, but better than keeping bootstraps broken until the root cause is debugged and fixed. Tested with a

[Bug tree-optimization/51084] bounds checking not optimized to a single comparison

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51084 Paul Eggert changed: What|Removed |Added CC||eggert at cs dot ucla.edu --- Comment #4

[Bug c++/113976] [11/12/13/14 Regression] explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976 --- Comment #2 from Matthias Maier --- I have bisected the issue to: commit 2ec399d8a6c9c26d69b73faf77c694fa3915dcec (HEAD, refs/bisect/bad) Author: Joerg Sonnenberger Date: Fri Sep 1 10:26:00 2017 -0600 varasm.c (bss_initializer_p):