https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
David Malcolm changed:
What|Removed |Added
Blocks||99390
--- Comment #13 from David Malcolm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #12 from Mark Wielaard ---
(In reply to David Malcolm from comment #11)
> (In reply to Mark Wielaard from comment #10)
> > Created attachment 49293 [details]
> > supergraph
>
> Thanks. Compared to my testing, I'm seeing what appear
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #11 from David Malcolm ---
(In reply to Mark Wielaard from comment #10)
> Created attachment 49293 [details]
> supergraph
Thanks. Compared to my testing, I'm seeing what appear to be differences in
the inputs to the analyzer at the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #10 from Mark Wielaard ---
Created attachment 49293
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49293&action=edit
supergraph
> Mark: please can you add -fdump-analyzer-supergraph to the arguments and
> attach > the bzip2.c.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #9 from David Malcolm ---
The above patch fixes (a) from comment #7 above, but (b), (c) and (d) still
need fixing, so keeping this open for now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #8 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:d60d63a00bb50ba6896939705c589578177b404d
commit r11-3537-gd60d63a00bb50ba6896939705c589578177b404d
Author: David Malcolm
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #7 from David Malcolm ---
Thanks. I see a similar deluge of
"terminating analysis for this program point"
warnings, but at different locations.
My warnings eventually terminate with:
bzip2.c:1537:31: warning: analysis bailed ou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #6 from Mark Wielaard ---
Created attachment 49291
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49291&action=edit
Output for gcc -Wanalyzer-too-complex -g -O2 -fanalyzer -c bzip2.c
(In reply to David Malcolm from comment #5)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #5 from David Malcolm ---
Thanks Mark. What architecture are you on?
When I do those steps, there's a long wait and then in terminates with no
analyzer output.
If I add -Wanalyzer-too-complex I see lots of warnings about "terminati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #4 from Mark Wielaard ---
Note that I can replicate it with the instructions in the description and gcc
git: gcc (GCC) 11.0.0 20200916 (experimental)
$ /opt/local/install/gcc/bin/gcc -g -O2 -fanalyzer -c bzip2.c 2>&1 | head -25
bzip2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #3 from David Malcolm ---
Also, I can probably cook up a more minimal reproducer - but it would be good
to track down the state-explosion issues: scaling up -fanalyzer to deal
effectively with real-world C code is a goal for me for GC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
David Malcolm changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:b28491dc2d79763ecbff4f0b9f1f3e48a443be1d
commit r11-3245-gb28491dc2d79763ecbff4f0b9f1f3e48a443be1d
Author: David Malcolm
Date: Tu
13 matches
Mail list logo
