https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99854
jseward at acm dot org changed:
What|Removed |Added
Resolution|DUPLICATE |FIXED
--- Comment #2 from
oduct: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: jseward at acm dot org
Target Milestone: ---
Building Valgrind trunk on x86_64-linu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692
--- Comment #22 from jseward at acm dot org ---
Looking back at the above, it's now clearer what the problem is:
# Park potentially live data in the red zone
_savegpr0_14: std r14,-144(r1)
_savegpr0_15: std r15,-136(r1)
_savegpr0_16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692
--- Comment #21 from jseward at acm dot org ---
(In reply to Jakub Jelinek from comment #20)
> Can you disable it just for these magic entrypoints (either by name or by
> content)?
In principle yes. I prefer by-content rather than b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692
jseward at acm dot org changed:
What|Removed |Added
CC||jseward at acm dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9
--- Comment #7 from jseward at acm dot org ---
(In reply to Jakub Jelinek from comment #3)
> Because, say in the memcmp case, if the first 4 bytes are defined and are
> not equal to the first bytes of the other value, then it will be non
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9
--- Comment #6 from jseward at acm dot org ---
(In reply to Martin Liška from comment #5)
> >
> > That should make it run clean even without using
> > --expensive-definedness-checks=yes. Does it?
>
> Yes, as mentione
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9
jseward at acm dot org changed:
What|Removed |Added
CC||jseward at acm dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80479
jseward at acm dot org changed:
What|Removed |Added
CC||jseward at acm dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82888
--- Comment #2 from jseward at acm dot org ---
(In reply to Andrew Pinski from comment #1)
> -O3 produces the memset:
Having to go to -O3 to get reasonable code isn't a great solution, though.
Couldn't gcc at least produce a word-at-a-time l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70627
--- Comment #10 from jseward at acm dot org ---
Thank you for fixing this quickly!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70627
--- Comment #7 from jseward at acm dot org ---
I tried the fix at PR70029 comment 7 (disabling a check) but that
doesn't help, at least for the original, unreduced test case
(Unified_cpp_dom_animation0.ii).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70627
--- Comment #2 from jseward at acm dot org ---
Created attachment 38236
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38236=edit
Unified_cpp_dom_animation0.ii.bz2
Testcase .ii.bz2, compressed so as to get it under the 1MB limit :-(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70627
--- Comment #1 from jseward at acm dot org ---
sewardj@dundee[6X]:~/MOZ$ c++ -c Unified_cpp_dom_animation0.ii -Wall
-Wc++11-compat -Wempty-body -Wignored-qualifiers -Woverloaded-virtual
-Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable
++
Assignee: unassigned at gcc dot gnu.org
Reporter: jseward at acm dot org
Target Milestone: ---
This is with gcc (GCC) 6.0.0 20160410 (experimental) building part of Firefox
on x86_64-linux, on Fedora 21.
15 matches
Mail list logo
