https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095
--- Comment #5 from mengli ming ---
Created attachment 56202
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56202&action=edit
Under the `-O0` optimization level, irrelevant code affects whether the
analyzer will report an out-of-bound warn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095
--- Comment #4 from mengli ming ---
(In reply to David Malcolm from comment #1)
> Thanks for filing this bug.
>
> This looks similar to bug 111213.
>
> Adding -fdump-ipa-analyzer=stderr shows that at -O1 and above, the entire
> body of the fun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #4 from mengli ming ---
Hi, I've checked recently and the crash still persists, even with the -O0
optimization level.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095
--- Comment #3 from mengli ming ---
(In reply to David Malcolm from comment #1)
> Thanks for filing this bug.
>
> This looks similar to bug 111213.
>
> Adding -fdump-ipa-analyzer=stderr shows that at -O1 and above, the entire
> body of the fun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110520
--- Comment #2 from mengli ming ---
(In reply to David Malcolm from comment #1)
> Thanks for filing this bug.
>
> With trunk (for gcc 14) I correctly get a NPD warning (true positive):
> https://godbolt.org/z/a5h38cz7d
>
> With gcc 13.2, I d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111213
--- Comment #3 from mengli ming ---
(In reply to David Malcolm from comment #1)
> (In reply to mengli ming from comment #0)
>
> Thanks for filing this bug.
>
> > Hi, this case (https://godbolt.org/z/98PMz1KKz) contains an out-of-bound
> > erro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #3 from mengli ming ---
Um..regarding the warning about "stack-based buffer over-read", it's a FP.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
--- Comment #2 from mengli ming ---
(In reply to Andrew Pinski from comment #1)
> Created attachment 55916 [details]
> testcase
>
> Please next time attach or place the testcase inline instead of just linking
> to godbolt .
Thanks for the remi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
Bug ID: 111441
Summary: internal compiler error: in fold_binary_loc, at
fold-const.cc:11580
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110529
--- Comment #6 from mengli ming ---
(In reply to David Malcolm from comment #5)
> Should be fixed on trunk for gcc 14 by the above commit.
Thanks a lot for your hard work!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111213
Bug ID: 111213
Summary: -Wanalyzer-out-of-bounds false negative with `return
arr[9];`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110529
--- Comment #2 from mengli ming ---
Um, would you be available to take a look at this case? Your insights would be
greatly appreciated!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111095
Bug ID: 111095
Summary: -Wanalyzer-out-of-bounds false negative with `return
l_1322[9];`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110529
--- Comment #1 from mengli ming ---
It's a little odd that there is no output (https://godbolt.org/z/GhshzvaTq) for
`_analyzer_eval(1)` in line 9 and line 13.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110529
Bug ID: 110529
Summary: -Wanalyzer-null-dereference false nagetive with
`*arr[0] = 10086`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110521
Bug ID: 110521
Summary: -Wanalyzer-null-dereference false nagetive with `*p =
i`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110520
Bug ID: 110520
Summary: -Wanalyzer-null-dereference false nagetive with `*ptr
= 10086`
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
17 matches
Mail list logo