https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #32 from Vadim Zeitlin ---
(In reply to Martin Liška from comment #31)
> Created attachment 43781 [details]
> Partially reduced test-case
>
> I've got 120KB partially reduced test-case. Any further reduction is not
> much possible.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #31 from Martin Liška ---
Created attachment 43781
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43781=edit
Partially reduced test-case
I've got 120KB partially reduced test-case. Any further reduction is not much
possible.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #30 from Martin Liška ---
(In reply to Martin Liška from comment #29)
> Thanks. I can't reproduce that on my openSUSE package nor on my build
> gcc-7-branch. However I downloaded Debian binary and I can confirm that.
> I'm bisecting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
Martin Liška changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #29 from Martin Liška
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #28 from Vadim Zeitlin ---
(In reply to Martin Liška from comment #26)
> complete output of:
> diff -u nowarn.s warn.s
Attached, but most of it is just noise from the label renumbering due to the
extra label being created, as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #27 from Vadim Zeitlin ---
Created attachment 43777
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43777=edit
Diff between assembly generated with and without the warning options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #26 from Martin Liška ---
complete output of:
diff -u nowarn.s warn.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #25 from Vadim Zeitlin ---
(In reply to Martin Liška from comment #24)
> > Please let me know if I can do anything else.
>
> Can you please attach full diff?
Sorry, diff between what and what?
> Am I correct that your native
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #24 from Martin Liška ---
> Please let me know if I can do anything else.
Can you please attach full diff? Am I correct that your native compiler is on
x86_64? Please attach output of --verbose.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #23 from Vadim Zeitlin ---
Just to confirm that this is not specific to MinGW-w64, I've attached the test
case (and a preprocessed version of it) allowing to reproduce the same problem
with Linux x86_64 version of g++ 7.3 (7.3.0-12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #22 from Vadim Zeitlin ---
Created attachment 43775
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43775=edit
Compressed preprocessed test case for native Linux gcc 7.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #21 from Vadim Zeitlin ---
Created attachment 43774
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43774=edit
Reduced test case showing the problem with native g++ 7.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #20 from Mathieu Malaterre ---
(In reply to Martin Liška from comment #19)
> (In reply to Mathieu Malaterre from comment #18)
> > The first diff seems to be here:
> >
> > +Use of uninitialised value of size 8
> > + at 0x98CBD7:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #18 from Mathieu Malaterre ---
The first diff seems to be here:
+Use of uninitialised value of size 8
+ at 0x98CBD7: sparseset_bit_p (sparseset.h:147)
+ by 0x98CBD7: process_bb_node_lives(ira_loop_tree_node*) (ira-lives.c:1226)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #17 from Mathieu Malaterre ---
Here is what I did over here:
# debootstrap --arch amd64 sid /srv/chroot/sid-amd64
http://httpredir.debian.org/debian
# mount -t proc proc /srv/chroot/sid-amd64/proc
# chroot /srv/chroot/sid-amd64 apt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #16 from Vadim Zeitlin ---
(In reply to Alexander Monakov from comment #13)
> It corresponds to
>
> if(!(!std::signbit(bourn_cast( From(0) {
> lmi_test::record_error(); };
> if(!(std::signbit(bourn_cast(-From(0) {
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
Mathieu Malaterre changed:
What|Removed |Added
CC||mathieu.malaterre at gmail dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #15 from Mathieu Malaterre ---
Created attachment 43773
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43773=edit
valgrind output (not ok)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #13 from Alexander Monakov ---
> (in the diffs, plus-lines correspond to -Wnonnull added to command line)
No, sorry, it was the other way around. Here's the reverse diff with more
context:
if (0)
{
<;
}
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #12 from Alexander Monakov ---
I can reproduce it with downloaded Debian's cc1plus, and for me -Wnonnull alone
is sufficient to cause diverging codegen. It diverges very early, in the
frontend: diff of .tu dumps starts with:
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #11 from Vadim Zeitlin ---
(In reply to Alexander Monakov from comment #8)
> Vadim, can you please check if the issue is reproducible on preprocessed
> (-E) input as well,
Yes, it is. I've actually started with the preprocessed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #10 from Vadim Zeitlin ---
Created attachment 43770
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43770=edit
Compressed preprocessed test case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #9 from Vadim Zeitlin ---
Another data point: I can also reproduce the problem with the native (i.e.
Linux) g++ 7.3 (Debian 7.3.0-12), although it looks slightly differently there:
all 3 of the following commands produce different
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #7 from Jonathan Wakely ---
(In reply to rguent...@suse.de from comment #5)
> It was whether the file was in a subdirectory or in the cwd, not
> whether the warnings were used.
Both:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #6 from Vadim Zeitlin ---
(In reply to Jonathan Wakely from comment #4)
> I can't reproduce this with:
> gcc version 7.2.0 20170814 (Fedora MinGW 7.2.0-1.fc26) (GCC)
Thanks for testing! So this would seem to indicate that the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #5 from rguenther at suse dot de ---
On Tue, 27 Mar 2018, redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
>
> --- Comment #4 from Jonathan Wakely ---
> I can't reproduce this with:
> gcc version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #4 from Jonathan Wakely ---
I can't reproduce this with:
gcc version 7.2.0 20170814 (Fedora MinGW 7.2.0-1.fc26) (GCC)
I get one warning:
$ i686-w64-mingw32-g++ -c -std=c++17 -Wnonnull -Woverloaded-virtual -O2
16795.cpp
16795.cpp:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #3 from Vadim Zeitlin ---
(In reply to Richard Biener from comment #2)
> This looks like a GC / memory corruption issue to me. Can you check whether
> using -fchecking uncovers anything?
Using -fchecking doesn't change anything,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85091
--- Comment #1 from Vadim Zeitlin ---
Created attachment 43768
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43768=edit
Test script used with delta, also useful for testing
32 matches
Mail list logo
