https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109548
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-04-19
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71850
--- Comment #8 from Costas Argyris ---
Not likely to be fixed, so if someone stumbles upon this and needs a
workaround, you need to override the default specs as in the example above.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109550
--- Comment #2 from Frank Heckenbach ---
It might be useful then to actually say to in the warning, e.g. "p[...] may be
used uninitialized". This might have saved me some debugging effort.
But actually, that's not all. This code still gives
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108840
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108840
--- Comment #4 from CVS Commits ---
The master branch has been updated by Kyrylo Tkachov :
https://gcc.gnu.org/g:136330bf637b50a4f10ace017a4316541386b9c0
commit r14-62-g136330bf637b50a4f10ace017a4316541386b9c0
Author: Kyrylo Tkachov
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109551
Bug ID: 109551
Summary: Show location where implicit instantiation first
required
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109237
--- Comment #13 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:8f81100115f68b37fb2723e987c14a3185d1f47d
commit r14-60-g8f81100115f68b37fb2723e987c14a3185d1f47d
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109524
--- Comment #13 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:865d712a9a20eed444ce61a0a0106534479bedf1
commit r13-7224-g865d712a9a20eed444ce61a0a0106534479bedf1
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109524
--- Comment #12 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:794ffdb0fb6312ce07af0bfc797bef9f4cff4c61
commit r14-59-g794ffdb0fb6312ce07af0bfc797bef9f4cff4c61
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109550
Richard Biener changed:
What|Removed |Added
Blocks||24639
--- Comment #1 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
Richard Biener changed:
What|Removed |Added
Keywords||testsuite-fail
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109546
Richard Biener changed:
What|Removed |Added
Summary|[13 Regression] Missed |[13/14 Regression] Missed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109550
Bug ID: 109550
Summary: warning: "p" may be used uninitialized
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
--- Comment #2 from Andrew Pinski ---
Note for some x86 cores having 2 or more cmove back to back is worse than a
conditional jump so maybe the testcase is now catching what it should happen
...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
--- Comment #1 from Andrew Pinski ---
> BTW, I saw Andrew's patch fixing cmov:
It is unrelated. This is a cost model issue of the x86 backend I think.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
Bug ID: 109549
Summary: [14 Regression] cmov6.c test fail after commit
r14-53-g675b1a7f113adb1d737adaf78b4fd90be7a0ed1a
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #7 from Puneet B ---
Any pointers here help to debug further.
101 - 118 of 118 matches
Mail list logo