https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102486
Luc Van Oostenryck changed:
What|Removed |Added
CC||luc.vanoostenryck at gmail dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100377
--- Comment #3 from Luc Van Oostenryck ---
> I thought there was one which I filed which is much older than those but I
> can't find it.
Probably also related to PR36409 and PR49157
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Created attachment 50727
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50727&action=edit
testcase
O
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Created attachment 50726
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50726&action=edit
testcases
When co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100075
--- Comment #4 from Luc Van Oostenryck ---
(In reply to Jakub Jelinek from comment #3)
> Fixed on the trunk. Probably shouldn't be backported.
Work great here. Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100056
--- Comment #11 from Luc Van Oostenryck ---
Works nicely now.
Thank you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100028
--- Comment #8 from Luc Van Oostenryck ---
Woks nicely now.
Thanks
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Target: aarch64
Created attachment 50588
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50588&acti
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Target: aarch64
Created attachment 50587
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50587&acti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100056
--- Comment #7 from Luc Van Oostenryck ---
Created attachment 50585
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50585&action=edit
newer testcases (with 32 -> 64-bit extensions)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100056
--- Comment #6 from Luc Van Oostenryck ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 50583 [details]
> gcc11-pr100056.patch
>
> Untested fix.
OTOH, for the signed case things seems to be OK unless the
sign extension is o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100056
--- Comment #5 from Luc Van Oostenryck ---
Created attachment 50584
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50584&action=edit
updated test cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100056
--- Comment #4 from Luc Van Oostenryck ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 50583 [details]
> gcc11-pr100056.patch
>
> Untested fix.
Mmmm, that's working fine for the cases I had but not in
more general cases. I
: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Target: aarch64
Created attachment 50573
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50573&action=edit
or-shift vs. [us]bfiz
On arm64, the followi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100028
--- Comment #5 from Luc Van Oostenryck ---
(In reply to Jakub Jelinek from comment #4)
> Created attachment 50571 [details]
> gcc11-pr100028.patch
>
> Untested fix.
This solve the few cases I had.
Thanks.
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Created attachment 50569
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50569&action=edit
compare with itself
The attach
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Target: aarch64
Created attachment 50555
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50555&action=edit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92935
Luc Van Oostenryck changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95379
--- Comment #14 from Luc Van Oostenryck ---
(In reply to Tom Tromey from comment #7)
> The feature was added specifically to mimic what sparse does.
> If sparse changes, I think changing gcc would be appropriate.
Sparse warnings issued when usin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95379
--- Comment #11 from Luc Van Oostenryck ---
(In reply to Andrew Pinski from comment #10)
> GCC uses -Wno-designated-init to disable the warning (this option has been
> there included for a while)? Do you think sparse could add/use the same
> opt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95379
Luc Van Oostenryck changed:
What|Removed |Added
CC||luc.vanoostenryck at gmail dot
com
IRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
Created attachment 47495
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47495&action=ed
Assignee: unassigned at gcc dot gnu.org
Reporter: luc.vanoostenryck at gmail dot com
Target Milestone: ---
gcc doesn't issue a warning for very simple cases of uninitialized variable.
The options used are '-Wuninitialized -O2' or '-Wmaybe-uninitial
23 matches
Mail list logo