public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
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 17:40:00 -0000 [thread overview]
Message-ID: <bug-66563-4-rXz50NjUK7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66563-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563
--- Comment #22 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Oleg Endo from comment #20)
> (In reply to John Paul Adrian Glaubitz from comment #16)
> > ...
> > 763a3c: 03 61 mov r0,r1
> > 763a3e: 00 e3 mov #0,r3
> > 763a40: 16 62 mov.l @r1+,r2
> > 763a42: 3c 22 cmp/str r3,r2
> > 763a44: fc 8b bf 763a40
> > ...
>
> That's a code snippet of the builtin strlen which has been added in 4.9...
That's strange. As Kaz has observed correctly, gcc always seems to segfault
when it comes to float arithmetics as I posted in #7.
Provided that you're right, how would a bug in strlen this explain that gcc
always segfaults when it needs to do float arithmetics?
Hmm.
I will do some further testing with a downgraded libmpfr.
>From gcc-bugs-return-489501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jun 20 17:50:33 2015
Return-Path: <gcc-bugs-return-489501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61628 invoked by alias); 20 Jun 2015 17:50:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61602 invoked by uid 48); 20 Jun 2015 17:50:29 -0000
From: "tps@vr-web.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/66104] svn co https://gcc.gnu.org/svn/gcc/branches/gcc-5-branch/
Date: Sat, 20 Jun 2015 17:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tps@vr-web.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66104-4-Van31QD9AZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66104-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66104-4@http.gcc.gnu.org/bugzilla/>
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/msg01833.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf104
--- Comment #7 from Thomas Schweikle <tps@vr-web.de> ---
If it wouldn't be possible to migrate up to 1.7.x or 1.8.x.
1.6.23 is the last version packaged of the 1.6-stream.
next prev parent reply other threads:[~2015-06-20 17:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 8:59 [Bug target/66563] New: " doko at gcc dot gnu.org
2015-06-17 10:05 ` [Bug target/66563] " glaubitz at physik dot fu-berlin.de
2015-06-17 10:12 ` rguenth at gcc dot gnu.org
2015-06-17 12:54 ` glaubitz at physik dot fu-berlin.de
2015-06-19 10:27 ` glaubitz at physik dot fu-berlin.de
2015-06-19 10:27 ` glaubitz at physik dot fu-berlin.de
2015-06-19 11:55 ` kkojima at gcc dot gnu.org
2015-06-19 13:13 ` glaubitz at physik dot fu-berlin.de
2015-06-19 13:26 ` glaubitz at physik dot fu-berlin.de
2015-06-19 13:29 ` glaubitz at physik dot fu-berlin.de
2015-06-19 13:29 ` glaubitz at physik dot fu-berlin.de
2015-06-19 13:36 ` glaubitz at physik dot fu-berlin.de
2015-06-19 13:59 ` kkojima at gcc dot gnu.org
2015-06-19 14:27 ` glaubitz at physik dot fu-berlin.de
2015-06-19 15:17 ` kkojima at gcc dot gnu.org
2015-06-19 17:34 ` glaubitz at physik dot fu-berlin.de
2015-06-19 21:56 ` kkojima at gcc dot gnu.org
2015-06-20 9:31 ` glaubitz at physik dot fu-berlin.de
2015-06-20 12:29 ` kkojima at gcc dot gnu.org
2015-06-20 13:41 ` olegendo at gcc dot gnu.org
2015-06-20 17:40 ` glaubitz at physik dot fu-berlin.de [this message]
2015-06-21 0:24 ` glaubitz at physik dot fu-berlin.de
2015-06-22 2:25 ` olegendo at gcc dot gnu.org
2015-06-22 13:23 ` glaubitz at physik dot fu-berlin.de
2015-06-22 18:21 ` glaubitz at physik dot fu-berlin.de
2015-06-23 3:03 ` kkojima at gcc dot gnu.org
2015-06-23 3:06 ` kkojima at gcc dot gnu.org
2015-06-23 13:24 ` olegendo at gcc dot gnu.org
2015-06-24 14:04 ` olegendo at gcc dot gnu.org
2015-06-25 10:16 ` kkojima at gcc dot gnu.org
2015-06-26 20:04 ` jakub at gcc dot gnu.org
2015-06-26 20:32 ` jakub at gcc dot gnu.org
2015-07-01 5:42 ` glaubitz at physik dot fu-berlin.de
2015-07-01 19:06 ` glaubitz at physik dot fu-berlin.de
2015-07-01 19:58 ` glaubitz at physik dot fu-berlin.de
2015-07-01 22:41 ` kkojima at gcc dot gnu.org
2015-07-05 22:28 ` glaubitz at physik dot fu-berlin.de
2015-07-05 23:20 ` glaubitz at physik dot fu-berlin.de
2015-07-06 0:49 ` glaubitz at physik dot fu-berlin.de
2015-07-06 15:22 ` glaubitz at physik dot fu-berlin.de
2015-07-09 21:12 ` [Bug target/66563] [4.9/5 " doko at gcc dot gnu.org
2015-07-09 21:19 ` glaubitz at physik dot fu-berlin.de
2015-07-09 22:39 ` kkojima at gcc dot gnu.org
2015-07-09 23:03 ` kkojima at gcc dot gnu.org
2015-07-10 10:03 ` kkojima at gcc dot gnu.org
2015-07-10 10:20 ` glaubitz at physik dot fu-berlin.de
2015-07-26 5:11 ` olegendo at gcc dot gnu.org
2015-07-26 16:34 ` glaubitz at physik dot fu-berlin.de
2015-07-27 3:53 ` olegendo at gcc dot gnu.org
2015-08-20 8:16 ` glaubitz at physik dot fu-berlin.de
2015-08-20 8:21 ` glaubitz at physik dot fu-berlin.de
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-66563-4-rXz50NjUK7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).