[Bug tree-optimization/104655] [12 Regression] array subscript 0 is outside array bounds of

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104655 --- Comment #7 from Paul Menzel --- Thank you for the analysis. Excuse my ignorance, but the referenced bug (possible dup) says it’s a regression in GCC 11, but it does not show up here with GCC 11. Are more issues tracked in bug 99578?

[Bug tree-optimization/104655] [12 Regression] array subscript 0 is outside array bounds of

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104655 --- Comment #5 from Paul Menzel --- Created attachment 52498 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52498&action=edit Preprocessed file `build/bootblock/cpu/x86/lapic/lapic.i` with `-save-temps` Sorry for not sharing the file in t

[Bug tree-optimization/104655] [12 Regression] array subscript 0 is outside array bounds of

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104655 --- Comment #3 from Paul Menzel --- (In reply to Andrew Pinski from comment #2) > I am 90% sure this is just another dup of bug 99578. Are you sure, because the warnings/errors are not there with GCC 11.

[Bug tree-optimization/104655] New: [12 Regression] array subscript 0 is outside array bounds of

Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: pmenzel+gcc at molgen dot mpg.de Target Milestone: --- Building SeaBIOS and coreboot with GCC 12 from Debian sid/unstable gcc-12 (Debian 12-20220222-1) 12.0.1 20220222

[Bug middle-end/99578] [11/12 Regression] gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #21 from Paul Menzel --- Created attachment 52193 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52193&action=edit [SeaBIOS] [PATCH] smm: Suppress gcc array-bounds warnings For the record, I attach Kevin’s patch used to work ar

[Bug middle-end/99578] [11/12 Regression] gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #20 from Paul Menzel --- (In reply to Andrew Pinski from comment #19) > *** Bug 103768 has been marked as a duplicate of this bug. *** It’d be great, if you could advise how to address the warning in SeaBIOS. In file included fr

[Bug c/103768] New: array-bounds warning for `memcpy((void*)0x1234, p, n)`, where n is greater than 8

Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pmenzel+gcc at molgen dot mpg.de Target Milestone: --- In the SeaBIOS list thread *[PATCH] memmap: Fix gcc out-of-bounds warning* [1], the array out of bounds warning

[Bug target/100771] Types differ between i386-elf and x86_64-elf -m32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100771 Paul Menzel changed: What|Removed |Added CC||pmenzel+gcc at molgen dot mpg.de

[Bug c/100771] New: Types differ between i386-elf and x86_64-elf -m32

Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pmenzel+gcc at molgen dot mpg.de Target Milestone: --- coreboot still builds 32-bit objects(?), and passes `-m32` for “64-bit compilers”. Doing that, sometimes there are type differences, which is unexpected. For GCC

[Bug c/82118] Instruction `lsrsne` unknown

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

[Bug c/82118] New: Instruction `lsrsne` unknown

Assignee: unassigned at gcc dot gnu.org Reporter: pmenzel+gcc at molgen dot mpg.de Target Milestone: --- >From the discussion of a change-set for coreboot [1], it turns out that GCC does not understand valid instructions. ``` $ arm-linux-gnueabi-gcc-7 --version arm-linux-gnueabi-gcc-7 (Deb