public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thomas.petazzoni@free-electrons.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65151] [SH][4.9 Regression] Internal compiler error when trying to build libav 11.2 on sh4
Date: Sat, 08 Aug 2015 15:24:00 -0000	[thread overview]
Message-ID: <bug-65151-4-TMXjnZHynu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65151-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65151

--- Comment #13 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
(In reply to John Paul Adrian Glaubitz from comment #12)
> (In reply to Thomas Petazzoni from comment #11)
> > (In reply to Jakub Jelinek from comment #10)
> > > GCC 4.9.3 has been released.
> > 
> > This problem still occurs with GCC 4.9.3, as far as I can see.
> 
> I'm actually not sure. There have been many changes to the SH backend ever
> since and as Debian moved from libav to ffmpeg as the default library, I
> haven't had a chance to test-build libav for a long time.

I am quite sure, see
http://autobuild.buildroot.org/results/09b/09b08d329e632365dd8371371706dbeaa10539a3/build-end.log:

libavcodec/dpxenc.c: In function 'encode_frame':
libavcodec/dpxenc.c:162:1: internal compiler error: in
elimination_costs_in_insn, at reload1.c:3638

The toolchain, available at
http://autobuild.buildroot.org/toolchains/tarballs/br-sh4-full-2015.05-496-g85945aa.tar.bz2,
uses gcc 4.9.3.


      parent reply	other threads:[~2015-08-08 15:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  4:48 [Bug c/65151] New: " glaubitz at physik dot fu-berlin.de
2015-02-21 13:29 ` [Bug target/65151] " olegendo at gcc dot gnu.org
2015-02-21 14:16 ` glaubitz at physik dot fu-berlin.de
2015-02-21 14:47 ` [Bug target/65151] [SH][4.9 Regression] " olegendo at gcc dot gnu.org
2015-02-21 21:29 ` olegendo at gcc dot gnu.org
2015-02-21 23:09 ` olegendo at gcc dot gnu.org
2015-02-21 23:26 ` olegendo at gcc dot gnu.org
2015-02-22 14:17 ` olegendo at gcc dot gnu.org
2015-02-23  0:00 ` kkojima at gcc dot gnu.org
2015-02-23 11:07 ` rguenth at gcc dot gnu.org
2015-06-26 19:59 ` jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.org
2015-08-08 14:54 ` thomas.petazzoni@free-electrons.com
2015-08-08 15:09 ` glaubitz at physik dot fu-berlin.de
2015-08-08 15:24 ` thomas.petazzoni@free-electrons.com [this message]

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-65151-4-TMXjnZHynu@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).