From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3515 invoked by alias); 20 Jun 2015 09:31:10 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 3414 invoked by uid 48); 20 Jun 2015 09:31:05 -0000 From: "glaubitz at physik dot fu-berlin.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66563] [4.9 Regression] ICE (segmentation fault) on sh4-linux-gnu Date: Sat, 20 Jun 2015 09:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-06/txt/msg01814.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563 --- Comment #18 from John Paul Adrian Glaubitz --- (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