[Bug target/116174] [14/15 regression] Alignment request is added before endbr with -fcf-protection=branch since r15-888-gb644126237a1aa

2024-08-09 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116174 --- Comment #7 from Arnd Bergmann --- I confirmed that the patch from comment #6 addresses the build warnings I see in the kernel.

[Bug sanitizer/113214] false-positive -Wstringop-overflow warning with thread sanitizer

2024-02-05 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113214 --- Comment #2 from Arnd Bergmann --- The warning is now turned off in the kernel as a workaround: https://lore.kernel.org/all/CAHk-=whzbdlc024nxgjesfoopj9bo2bkuxhxr4h5wosyk9a...@mail.gmail.com/ Also, my local one-line workaround is applied fo

[Bug sanitizer/113214] New: false-positive -Wstringop-overflow warning with thread sanitizer

2024-01-03 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113214 Bug ID: 113214 Summary: false-positive -Wstringop-overflow warning with thread sanitizer Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/108402] False positive Wuninitialized with ftrivial-auto-var-init=pattern

2023-07-19 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108402 Arnd Bergmann changed: What|Removed |Added CC||arnd at linaro dot org --- Comment #7 f

[Bug c/110743] New: Unexpected -ftrivial-auto-var-init=pattern behavior with partial bitfields

2023-07-19 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110743 Bug ID: 110743 Summary: Unexpected -ftrivial-auto-var-init=pattern behavior with partial bitfields Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: n

[Bug sanitizer/110074] New: code bloat with -fprofile-args + -fsanitize=bounds

2023-06-01 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110074 Bug ID: 110074 Summary: code bloat with -fprofile-args + -fsanitize=bounds Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Compo

[Bug libgcc/108433] New: canadian cross aarch64/x86_64/aarch64 fails to build

2023-01-17 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108433 Bug ID: 108433 Summary: canadian cross aarch64/x86_64/aarch64 fails to build Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon

[Bug target/105930] [12/13 Regression] Excessive stack spill generation on 32-bit x86

2022-06-16 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930 Arnd Bergmann changed: What|Removed |Added CC||arnd at linaro dot org --- Comment #19

[Bug c/104711] New: Unnecessary -Wshift-negative-value warning

2022-02-27 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104711 Bug ID: 104711 Summary: Unnecessary -Wshift-negative-value warning Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug middle-end/102162] Byte-wise access optimized away at -O1 and above

2021-09-02 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102162 --- Comment #27 from Arnd Bergmann --- The linux kernel instance from arch/parisc/ looks like a bug we fixed in arch/arm a few years ago, by adding the required alignment directive to the linker script. If changing the linker script is not poss

[Bug tree-optimization/102162] Byte-wise access optimized away at -O1 and above

2021-09-01 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102162 Arnd Bergmann changed: What|Removed |Added CC||arnd at linaro dot org --- Comment #2 f

[Bug sanitizer/99673] [11 Regression] bogus -Wstringop-overread warning with address sanitizer due to member address substitution

2021-03-22 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673 --- Comment #4 from Arnd Bergmann --- I posted a set of kernel patches to address all the warnings I found at https://lore.kernel.org/lkml/20210322160253.4032422-1-a...@kernel.org/T/#t

[Bug sanitizer/99673] [11 Regression] bogus -Wstringop-overread warning with address sanitizer due to member address substitution

2021-03-20 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673 --- Comment #2 from Arnd Bergmann --- Thank you for the detailed analysis. This was the last such warning I get with linux kernel randconfig build that I could not explain based on the earlier discussion, so now I can submit the local workarounds

[Bug sanitizer/99673] New: [11 Regression] bogus -Wstringop-overread warning with address sanitizer

2021-03-19 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673 Bug ID: 99673 Summary: [11 Regression] bogus -Wstringop-overread warning with address sanitizer Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/92860] [8/9/10/11 regression] Global flags affected by -O settings are clobbered by optimize attribute

2021-03-16 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860 Bug 92860 depends on bug 99592, which changed state. Bug 99592 Summary: arm: internal compiler error using arm_neon.h with -pg https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99592 What|Removed |Added -

[Bug target/99592] arm: internal compiler error using arm_neon.h with -pg

2021-03-16 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99592 Arnd Bergmann changed: What|Removed |Added Status|RESOLVED|WAITING Resolution|FIXED

[Bug target/99592] arm: internal compiler error using arm_neon.h with -pg

2021-03-16 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99592 --- Comment #6 from Arnd Bergmann --- Created attachment 50395 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50395&action=edit preprocessed /usr/lib/gcc-cross/arm-linux-gnueabihf/11/include/arm_neon.h I've changed from the Ubuntu gcc-11 s

[Bug target/99600] [11 regression] out of memory for simple test case (x86 -march=atom) since r11-7274

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99600 --- Comment #9 from Arnd Bergmann --- I now built gcc with and without the patch from attachment 50390 to find more broken kernel configurations and verify that they are all fixed. So far, all the broken configurations are fixed by the patch, I'l

[Bug target/99592] arm: internal compiler error using arm_neon.h with -pg

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99592 --- Comment #4 from Arnd Bergmann --- $ arm-linux-gnueabihf-gcc-11 -v Using built-in specs. COLLECT_GCC=arm-linux-gnueabihf-gcc-11 COLLECT_LTO_WRAPPER=/usr/lib/gcc-cross/arm-linux-gnueabihf/11/lto-wrapper Target: arm-linux-gnueabihf Configured wi

[Bug target/99592] arm: internal compiler error using arm_neon.h with -pg

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99592 Arnd Bergmann changed: What|Removed |Added CC||doko at gcc dot gnu.org --- Comment #2 f

[Bug target/99600] [11 regression] out of memory for simple test case (x86 -march=atom)

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99600 Arnd Bergmann changed: What|Removed |Added CC||jakub at redhat dot com --- Comment #2 f

[Bug target/99600] [11 regression] out of memory for simple test case (x86 -march=atom)

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99600 --- Comment #1 from Arnd Bergmann --- https://godbolt.org/z/z7h7r3

[Bug target/99600] New: [11 regression] out of memory for simple test case (x86 -march=atom)

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99600 Bug ID: 99600 Summary: [11 regression] out of memory for simple test case (x86 -march=atom) Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug target/99596] New: arm: internal error in single_pred_edge

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99596 Bug ID: 99596 Summary: arm: internal error in single_pred_edge Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug target/99592] New: arm: internal compiler error using arm_neon.h with -pg

2021-03-15 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99592 Bug ID: 99592 Summary: arm: internal compiler error using arm_neon.h with -pg Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon

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

2021-03-14 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #6 from Arnd Bergmann --- I figured out the qnx4 warning in the end: https://godbolt.org/z/hvqjr3 struct qnx4_inode_entry { char di_status; union { struct { char di_fname[16]; char di_pad[32];

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

2021-03-14 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #5 from Arnd Bergmann --- (In reply to Martin Sebor from comment #4) > Most warnings designed to detect invalid accesses (not just > -Wstringop-overread but also -Wstringop-overflow and > -Wformat-overflow/-truncation, -Wrestrict, and

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

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #3 from Arnd Bergmann --- After some more analysis, I found that the -Wstringop-overread warning only happens here (and presumably in all the other cases I found) because I disabled -Warray-bounds for gcc-11. I'm still looking at -Wa

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

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 --- Comment #2 from Arnd Bergmann --- Ok, I see. Thanks for the explanation! I found a couple other instances (so far all false positive) and will see if any of them have a sane workaround. I'll probably just turn off both flags globally for the

[Bug rtl-optimization/99567] internal error in extract_constrain_insn with asan-stack

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99567 Arnd Bergmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug rtl-optimization/99567] internal error in extract_constrain_insn with asan-stack

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99567 --- Comment #2 from Arnd Bergmann --- *** Bug 99570 has been marked as a duplicate of this bug. ***

[Bug target/99570] internal error in extract_constrain_insn

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99570 Arnd Bergmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED

[Bug rtl-optimization/99567] internal error in extract_constrain_insn with asan-stack

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99567 --- Comment #1 from Arnd Bergmann --- *** Bug 99574 has been marked as a duplicate of this bug. ***

[Bug target/99574] gcc-11 unrecognizable insn in extract_constrain_insn, at recog.c:2670

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99574 Arnd Bergmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED

[Bug c/99578] New: gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 Bug ID: 99578 Summary: gcc-11 -Warray-bounds or -Wstringop-overread warning when accessing a pointer from integer literal Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug target/99570] internal error in extract_constrain_insn

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99570 --- Comment #1 from Arnd Bergmann --- I suppose this is a duplicate of #99567 and #99574, these happen with different compiler flags, but the backtrace is always the same.

[Bug target/99574] New: gcc-11 unrecognizable insn in extract_constrain_insn, at recog.c:2670

2021-03-13 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99574 Bug ID: 99574 Summary: gcc-11 unrecognizable insn in extract_constrain_insn, at recog.c:2670 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug target/99570] New: internal error in extract_constrain_insn

2021-03-12 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99570 Bug ID: 99570 Summary: internal error in extract_constrain_insn Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug rtl-optimization/99567] New: internal error in extract_constrain_insn with asan-stack

2021-03-12 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99567 Bug ID: 99567 Summary: internal error in extract_constrain_insn with asan-stack Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Prior

[Bug sanitizer/97490] New: [10/11 Regression] false-positive -Wstringop-overflow= with address sanitizer

2020-10-19 Thread arnd at linaro dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97490 Bug ID: 97490 Summary: [10/11 Regression] false-positive -Wstringop-overflow= with address sanitizer Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: