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/67506] New: [SH][5]: error: unrecognizable insn when compiling texlive-binaries
Date: Tue, 08 Sep 2015 20:39:00 -0000 [thread overview]
Message-ID: <bug-67506-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67506
Bug ID: 67506
Summary: [SH][5]: error: unrecognizable insn when compiling
texlive-binaries
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: glaubitz at physik dot fu-berlin.de
CC: kkojima at gcc dot gnu.org, olegendo at gcc dot gnu.org
Target Milestone: ---
Target: sh*-*-*
Created attachment 36307
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36307&action=edit
Preprocessed source for tftopl.c
Hello!
I just noticed that we run into a new regression which seems to have been
introduced with gcc-5.
The compiler output is as follows:
gcc -DHAVE_CONFIG_H -I. -I../../../texk/web2c -I./w2c
-I/«PKGBUILDDIR»/Work/texk -I/«PKGBUILDDIR»/texk -Wimplicit -Wreturn-type -g
-O2 -c -o tftopl.o tftopl.c
tftopl.c: In function 'mainbody':
tftopl.c:1808:1: error: unrecognizable insn:
}
^
(insn 9938 541 9939 36 (set (reg:SI 147 t)
(eq:SI (and:SI (reg:HI 1069 [ *_271 ])
(const_int 128 [0x80]))
(const_int 0 [0]))) tftopl.c:1542 -1
(nil))
tftopl.c:1808:1: internal compiler error: in extract_insn, at recog.c:2343
0x83edf3 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../src/gcc/rtl-error.c:110
0x83ee2d _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
../../src/gcc/rtl-error.c:118
0x8139dd extract_insn(rtx_insn*)
../../src/gcc/recog.c:2343
0xba62f3 decompose_multiword_subregs
../../src/gcc/lower-subreg.c:1502
0xba731f execute
../../src/gcc/lower-subreg.c:1772
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
Preprocessed source stored into /tmp/ccRGajx7.out file, please attach this to
your bugreport.
A full build log can be found in [1]. The build log of a previous, successful
build with gcc-4.9 can be found in [2]. I am attaching the preprocessed source
which is mentioned in the build log.
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=texlive-bin&arch=sh4&ver=2015.20150524.37493-6&stamp=1440539292
> [2] https://buildd.debian.org/status/fetch.php?pkg=texlive-bin&arch=sh4&ver=2015.20150524.37493-5&stamp=1437123205
>From gcc-bugs-return-496684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Sep 08 21:16:08 2015
Return-Path: <gcc-bugs-return-496684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7746 invoked by alias); 8 Sep 2015 21:16:08 -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 7703 invoked by uid 48); 8 Sep 2015 21:16:05 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64249] Missing warning for if (A) else if (A)
Date: Tue, 08 Sep 2015 21:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to target_milestone
Message-ID: <bug-64249-4-hObfmfZbWL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64249-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64249-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-09/txt/msg00662.txt.bz2
Content-length: 563
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd249
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Target Milestone|--- |6.0
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I seem to have something that seemingly works for the C FE.
next reply other threads:[~2015-09-08 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 20:39 glaubitz at physik dot fu-berlin.de [this message]
2015-09-09 0:39 ` [Bug target/67506] [5/6 Regression][SH]: " kkojima at gcc dot gnu.org
2015-09-09 1:06 ` kkojima at gcc dot gnu.org
2015-09-09 12:11 ` olegendo at gcc dot gnu.org
2015-09-10 10:23 ` olegendo at gcc dot gnu.org
2015-09-10 14:54 ` olegendo at gcc dot gnu.org
2015-09-10 15:07 ` olegendo at gcc dot gnu.org
2015-09-11 9:50 ` glaubitz at physik dot fu-berlin.de
2015-09-11 10:58 ` olegendo at gcc dot gnu.org
2015-09-20 20:34 ` glaubitz at physik dot fu-berlin.de
2015-09-21 0:29 ` 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-67506-4@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).