This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/66563] [4.9 Regression] ICE (segmentation fault) on sh4-linux-gnu
- From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 20 Jun 2015 09:31:04 +0000
- Subject: [Bug target/66563] [4.9 Regression] ICE (segmentation fault) on sh4-linux-gnu
- Auto-submitted: auto-generated
- References: <bug-66563-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #18 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Kazumoto Kojima from comment #17)
> Which version of mpfr/gmp is used for compilers? mpfr has self
> test and you could run it with "make check" in its build directory.
You seem to be on to something here as, in fact, mpfr had problems previously
when built with "make check" [1]:
PASS: tcheck
PASS: tisnan
../../test-driver: line 107: 5759 Segmentation fault "$@" > $log_file
2>&1
FAIL: texceptions
PASS: tset_exp
I have to admit that I recently disabled checks during builds on some buildds
to speed up the build process and this may have triggered the whole dilemma.
Assuming that mpfr would be the origin of this, would this also explain the
segmentation faults in the recently compiled systemd package? Because
apparently the systemd binaries crash because gcc has produced broken code
here. Could it be possible that the compiler made some float calculation which
gave a weird result, embedded that into systemd which in turns segfaults?
Adrian
> [1] http://buildd.debian-ports.org/status/fetch.php?pkg=mpfr4&arch=sh4&ver=3.1.2-3&stamp=1425025691