https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #11 from David Binderman ---
(In reply to Martin Liška from comment #10)
> However, I see a segfault that happens for the code snippet now.
In the compiler or the generated code ?
No crashes here. Are you running an asan+ubsan gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #10 from Martin Liška ---
(In reply to David Binderman from comment #9)
> Created attachment 54463 [details]
> C source code
>
> After a further hour of reduction, a partially reduced program.
>
> cvise doesn't seem able to make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #9 from David Binderman ---
Created attachment 54463
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54463=edit
C source code
After a further hour of reduction, a partially reduced program.
cvise doesn't seem able to make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #8 from David Binderman ---
(In reply to David Binderman from comment #7)
> After about 20 minutes of reduction, cvise started going the wrong way.
Second reduction now running, with better script:
/usr/bin/gcc -c -w bug883.c && \
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
David Binderman changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #6 from Richard Biener ---
Huh, the change for sure triggered some latent issue, either in the testcase or
in GCC. More analysis is needed (the testcase is large and obfuscated...).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #5 from Jakub Jelinek ---
(In reply to David Binderman from comment #4)
> (In reply to Andrew Pinski from comment #3)
> > This also changes with -fno-strict-aliasing ...
>
> So does that mean that csmith is producing C code with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #4 from David Binderman ---
(In reply to Andrew Pinski from comment #3)
> This also changes with -fno-strict-aliasing ...
So does that mean that csmith is producing C code with UB and so
this bug isn't valid ?
It might also mean
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
--- Comment #3 from Andrew Pinski ---
This also changes with -fno-strict-aliasing ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P2
Summary|csmith: possible
11 matches
Mail list logo
