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: Wed, 17 Jun 2015 10:05:00 -0000	[thread overview]
Message-ID: <bug-66563-4-AyhGmyaAfe@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 #1 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
Hi Matthias!

Thanks for the bug report but I think this might actually a problem with the
host compiler or its libraries. I have seen segfaults in multiple packages now
[1-3] and so I am very sure this is not an issue with gcc but with the
gcc-4.9_4.9.2-20+sh4 package that I built.

The problem occurred after I built gcc-4.9_4.9.2-20+sh4 manually to re-add
libstdc++6 back which was missing yet and I am suspecting that I messed
something up while doing that. I have even seen segfaults during packages
postinst scripts, for example, so I suspect an issue with the libstdc++6
library being broken.

The buildd tirpitz is currently [4] building gcc-4.9_4.9.2-21 which will be
your vanilla gcc-4.9 package and I hope that this will fix the issue.

Cheers,
Adrian

> [1] http://buildd.debian-ports.org/status/fetch.php?pkg=gnutls28&arch=sh4&ver=3.3.15-7&stamp=1434506763
> [2] http://buildd.debian-ports.org/status/fetch.php?pkg=wmfire&arch=sh4&ver=1.2.4-1&stamp=1434405734
> [3] http://buildd.debian-ports.org/status/fetch.php?pkg=cdebconf&arch=sh4&ver=0.194&stamp=1434394400
> [4] http://buildd.debian-ports.org/status/package.php?p=gcc-4.9&suite=sid


  reply	other threads:[~2015-06-17 10:05 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 ` glaubitz at physik dot fu-berlin.de [this message]
2015-06-17 10:12 ` [Bug target/66563] " 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
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-AyhGmyaAfe@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).