https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114622
Willy Tarreau changed:
What|Removed |Added
CC||w at 1wt dot eu
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
--- Comment #19 from Willy Tarreau ---
Hello Richard,
Thanks for looking at this old issue.
> that means next_step will do the bad access of 'head' using the struct ref
> type.
Actually there's no bad access, as if you look closely, next_step(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
--- Comment #14 from Willy Tarreau ---
(In reply to Martin Sebor from comment #13)
> The patch was rejected so we'll have to live with a confusing warning.
sadly it's not the first one and I don't count the number of bugs I have
introduced in my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
--- Comment #9 from Willy Tarreau ---
Hi Richard,
indeed, the &curr->list == &head is the test for end of list that prevents any
bad access from happening.
I know that usually the right way to do this is by using a list element, but
sometimes i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Bug 56456 depends on bug 98503, which changed state.
Bug 98503 Summary: [11 regression] -Warray-bounds false positive with global
variables at -O2 since r11-3306-g3f9a497d1b0dd9da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
Wha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
Willy Tarreau changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Bug 56456 depends on bug 98503, which changed state.
Bug 98503 Summary: [11 regression] -Warray-bounds false positive with global
variables at -O2 since r11-3306-g3f9a497d1b0dd9da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
Wha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
Willy Tarreau changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
--- Comment #4 from Willy Tarreau ---
Hi Martin,
I'm sorry but I'm missing something, as this is how linked lists are
implemented everywhere nowadays. I'm not actually casting the pointer, it was
made for simplification. I'm only following the l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503
--- Comment #1 from Willy Tarreau ---
Re-reading godbolt's version more closely, it's just 1 day old (I thought I
read 20201010) so the issue is still valid.
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: w at 1wt dot eu
Target Milestone: ---
First, please note that I saw a handful of related reports but couldn't judge
if this one might be merged with another one; if you thi
--- Comment #19 from w at 1wt dot eu 2007-08-05 15:39 ---
Reproduced with trivial code. The reason is very simple : The asm code is
emitted in the .data section, because due to the -fno-unit-at-a-time argument,
the "interrupts" array is declared first and sets the current
12 matches
Mail list logo
