https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106032
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105774
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105685
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105554
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94756
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87204
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929
--- Comment #16 from jbeulich at suse dot com ---
(In reply to LIU Hao from comment #15)
> This is accepted by ML64:
>
> ```
> PUBLICmain
> EXTRN rip:DWORD
> _TEXT SEGMENT
> main PROC
> mov eax, DWORD PTR rip
> ret 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53932
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109724
--- Comment #7 from Richard Biener ---
The real issue is probably that when value-numbering
Value numbering stmt = iftmp.77_74 = PHI
Setting value number of iftmp.77_74 to iftmp.77_177 (changed)
iftmp.77_177 is available for iftmp.77_177
we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929
--- Comment #15 from LIU Hao ---
> Which as least MASM up to 12.x won't assemble. For one it complains about
> "rip" being undeclared. And then the load of "ecx" is _not_ a memory access
> (i.e. the "DWORD PTR" is ignored there). Which is in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109724
--- Comment #6 from Richard Biener ---
I checked 11 and 12 and they are not affected. We run in circles through
valueize_refs_1 in vn_reference_maybe_forwprop_address, repeatedly picking up
_24 = [(const struct SkDPoint
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109727
Bug ID: 109727
Summary: [13/14 Regression] -Warray-bounds false positive with
-fsanitize=undefined
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109724
Sam James changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929
--- Comment #14 from jbeulich at suse dot com ---
(In reply to LIU Hao from comment #13)
> MSVC outputs:
> ```
> get_value PROC ; COMDAT
> mov ecx, DWORD PTR eax
> mov rax, QWORD PTR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109724
Richard Biener changed:
What|Removed |Added
Keywords||needs-bisection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109723
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109721
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97122
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109723
--- Comment #2 from Sam James ---
Created attachment 54990
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54990=edit
reduced.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109714
--- Comment #2 from Richard Biener ---
This is likely a duplicate, the issue is that uninit diagnostics do not cope
well with loops and use/def predicates that eventually involve PHIs with
backedges.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662
--- Comment #7 from john.harper at vuw dot ac.nz ---
I hadn't thought about -std=gnu in this context but it would make sense
for std=gnu to give a warning for comma after namelist name if
std=legacy is going to allow it without one. You
201 - 221 of 221 matches
Mail list logo
