https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #16 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #15)
> This was a glibc issue.
>
> Fixed by glibc commit 5e49c52efdb37eb0aa315156f39056f25ff9ddaa (
> https://sourceware.org/git/?p=glibc.git;a=commit;
> h=5e49c52efd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #14 from Andrew Pinski ---
movdqa %xmm1, 16(%esp)
movdqa %xmm0, 32(%esp)
Maybe stack alignment for deconstructors.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #13 from Tammy Hsu ---
Hi Mikael,
My last comment probably is not clear enough. The import (testcase) I built on
RHEL 5.5 crashes on RHEL 5.5, but if I ran it on Fedora 19, it works.
So if you take the import you built on CentOS 5.8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #12 from Tammy Hsu ---
I installed the required i686 rpms on the Fedora 19 system, and the testcase
works without crash (using the /bin/g++).
I then built gcc481 on the Fedora 19 system, the testcase also works fine when
I compile/lin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #11 from Tammy Hsu ---
Thank you. Yes, on the fedora 19 systems, I don't have these 3 i686 rpms
installed. I will add them.
Do you have any comments on the crash issue we have on CentOS 5.8 or RHEL
5.5/RHEL 6.3 after building gcc481
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #9 from Tammy Hsu ---
I tried to run the g++ build on RHEL 5.5 on a RHEL 6.3 system, import seg
fault.
I then tried to rebuild gcc481 on RHEL 6.3 and rerun the testcase, it still
crash.
The glibc on RHEL 6.3 is glibc-2.12-1.80.el6.x8
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #8 from Tammy Hsu ---
Thanks a lot for trying rebuilding twice!!
you don't think it is caused by optimization code? if we use "-O2" or "-O3
-fno-tree-vectorize" then it won't seg fault
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #7 from Mikael Pettersson ---
CentOS 5.8 has an old binutils-2.17.50.0.6-20.el5_8.3. Building and installing
binutils-2.23.2 and rebuilding gcc-4.8.1 against that makes no difference,
./import still SEGVs. I'm beginning to suspect a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #6 from Mikael Pettersson ---
I've just bootstrapped gcc-4.8.1 on CentOS 5.8 (the closest I have to the OP's
RHEL 5.5), and LD_LIBRARY_PATH=. ./import does indeed SEGV there.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #5 from Mikael Pettersson ---
Unmodified FSF gcc-4.8.1 configured as follows:
/tmp/gcc-4.8.1/configure --prefix=/tmp/install --with-gmp=/path/to/my/gmp-5.1.2
--with-mpfr=/path/to/my/mpfr-3.1.2 --with-mpc=/path/to/my/mpc-1.0.1
--enable
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #4 from Tammy Hsu ---
Sorry, I forgot to mention that I need to set LD_LIBRARY_PATH to "." to run
import.
I build the gcc473 and gcc481 by using the same configuration and on the same
RHEL 5.5 system, however the gcc473 version works a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
--- Comment #3 from Mikael Pettersson ---
I can't reproduce the SEGV on Fedora 17 with gcc-4.8.1 -m32 or gcc-4.9 -m32.
However, I think the build recipe is flawed. If I follow it to the letter
(with -Wl,-rpath pointing to where I installed gcc-4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Severity|major
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58208
Tammy Hsu changed:
What|Removed |Added
Severity|normal |major
--- Comment #2 from Tammy Hsu ---
Can
16 matches
Mail list logo
