https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #18 from Andrew Pinski ---
(In reply to Kristian Spangsege from comment #13)
> I've now run into this problem too, and it seems to be general, not just
> limited to Ubuntu.
>
> There is the code that I compile:
So this comment #13 i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #17 from Jonathan Wakely ---
(In reply to Chip Salzenberg from comment #16)
> Still happening in 7.2
What is?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #16 from Chip Salzenberg ---
Still happening in 7.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #15 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #14)
> (In reply to Kristian Spangsege from comment #13)
> > I expect it to write `1`, not `0`.
>
> Which is not a segfault, so is a completely different problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #14 from Jonathan Wakely ---
(In reply to Kristian Spangsege from comment #13)
> I expect it to write `1`, not `0`.
Which is not a segfault, so is a completely different problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
Kristian Spangsege changed:
What|Removed |Added
CC||kristian.spangsege at gmail
dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #12 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #10)
> Use ldd to see which library is used at runtime. See what file that symlink
> points to. Compare with the version numbers of the releases.
>
> GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #11 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #10)
> Use ldd to see which library is used at runtime. See what file that symlink
> points to. Compare with the version numbers of the releases.
>
> GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #10 from Jonathan Wakely ---
Use ldd to see which library is used at runtime. See what file that symlink
points to. Compare with the version numbers of the releases.
GCC 4.9.0: libstdc++.so.6.0.20
GCC 5.1.0: libstdc++.so.6.0.21
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #9 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #8)
> That only shows how your gcc compiler was built. If I understand correctly
> the Ubuntu packages that provide libstdc++.so.6 come from a different bui
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #8 from Jonathan Wakely ---
(In reply to eyenseo from comment #7)
> (In reply to Jonathan Wakely from comment #6)
>
> Thanks for letting me know of the "importance-ignoring" one two less clicks
> next time ;)
Yes, you don't need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #7 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #6)
Thanks for letting me know of the "importance-ignoring" one two less clicks
next time ;)
I didn't include the segfault in the precompiled file as I w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #6 from Jonathan Wakely ---
(In reply to eyenseo from comment #3)
> I would like to know what a critical or major bug would be if a segfault is
> not? I think that a segfault is quite devastating, especially when working
> with error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #5 from eyenseo at gmail dot com ---
(In reply to Jonathan Wakely from comment #2)
> I can't reproduce this, it might be specific to Ubuntu, maybe caused by
> mixing gcc 4.9 with the lisbtdc++ from gcc 5 (which would mean this is PR
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #4 from eyenseo at gmail dot com ---
The ubuntu system I used is "normal" no testing / unstable.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #3 from eyenseo at gmail dot com ---
This bug does not appear in 5.3.0 - using Arch Linux.
I would like to know what a critical or major bug would be if a segfault is
not? I think that a segfault is quite devastating, especially when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
--- Comment #2 from Jonathan Wakely ---
I can't reproduce this, it might be specific to Ubuntu, maybe caused by mixing
gcc 4.9 with the lisbtdc++ from gcc 5 (which would mean this is PR 66438).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
Jonathan Wakely changed:
What|Removed |Added
Severity|critical|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191
eyenseo at gmail dot com changed:
What|Removed |Added
Attachment #37264|0 |1
is obsolete|
20 matches
Mail list logo
