public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59375] internal compiler error: in expand_shift_1, at expmed.c:2245
Date: Thu, 05 Dec 2013 18:43:00 -0000	[thread overview]
Message-ID: <bug-59375-4-nkpW1bwD1E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59375-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59375

--- Comment #5 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Nobuhiro Iwamatsu from comment #4)
> Oleg and Kojima-san, thanks for your work.
> 
> Yes, I was building on SH native.
> And I am using gcc 4.6.3 version in the host.

Iwamatsu-san, if you have some time, could you please try building GCC 4.9? 
I'm sorry, but I don't have the right setup at hand to do it myself at the
moment.

Also, please notice that the current GCC 4.8 branch has some known problems in
the SH parts (produces wrong code) -- I'm working on back porting some patches
from 4.9.


  parent reply	other threads:[~2013-12-05 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  6:51 [Bug bootstrap/59375] New: " iwamatsu at nigauri dot org
2013-12-03 22:13 ` [Bug target/59375] " olegendo at gcc dot gnu.org
2013-12-04 20:41 ` olegendo at gcc dot gnu.org
2013-12-05  0:23 ` kkojima at gcc dot gnu.org
2013-12-05  0:58 ` iwamatsu at nigauri dot org
2013-12-05 18:43 ` olegendo at gcc dot gnu.org [this message]
2013-12-06  0:37 ` iwamatsu at nigauri dot org
2015-02-12 11:23 ` olegendo at gcc dot gnu.org
2015-02-17 21:24 ` olegendo at gcc dot gnu.org
2015-02-17 21:29 ` glaubitz at physik dot fu-berlin.de
2015-02-17 21:35 ` olegendo at gcc dot gnu.org

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-59375-4-nkpW1bwD1E@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).