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/65153] New: sh: "insn does not satisfy its constraints" when compiling libmcrypt
Date: Sat, 21 Feb 2015 09:52:00 -0000	[thread overview]
Message-ID: <bug-65153-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65153
           Summary: sh: "insn does not satisfy its constraints" when
                    compiling libmcrypt
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: glaubitz at physik dot fu-berlin.de
            Target: sh*-*-*

Hi!

Another regression in gcc-4.9.2, this time when trying to compile libmcrypt
2.5.8:

libtool: link: ( cd ".libs" && rm -f "arcfour.la" && ln -s "../arcfour.la"
"arcfour.la" )
/bin/sh ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H  -I.
-I../.. -I. -I../..  -I../../lib    -g -O2 -c -o cast-256.lo cast-256.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I../.. -I../../lib -g
-O2 -c cast-256.c  -fPIC -DPIC -o .libs/cast-256.o
cast-256.c: In function 'cast_256_LTX__mcrypt_set_key':
cast-256.c:409:1: error: insn does not satisfy its constraints:
 }
 ^
(insn 143 142 144 12 (set (reg/v:SI 7 r7 [orig:227 t ] [227])
        (ior:SI (reg:SI 1 r1)
            (reg:SI 13 r13 [orig:718 D.4992 ] [718]))) cast-256.c:387 130
{*iorsi3_compact}
     (expr_list:REG_DEAD (reg:SI 13 r13 [orig:718 D.4992 ] [718])
        (nil)))
cast-256.c:409:1: internal compiler error: in copyprop_hardreg_forward_1, at
regcprop.c:775
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
Preprocessed source stored into /tmp/ccwCPfub.out file, please attach this to
your bugreport.

Full build log can be found in [1]. Attaching the precompiled source file
ccwCPfub.out.

Adrian

> [1] http://buildd.debian-ports.org/status/fetch.php?pkg=libmcrypt&arch=sh4&ver=2.5.8-3.3&stamp=1424499784


             reply	other threads:[~2015-02-21  7:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  9:52 glaubitz at physik dot fu-berlin.de [this message]
2015-02-21 13:46 ` [Bug target/65153] " olegendo at gcc dot gnu.org
2015-02-21 14:41 ` glaubitz at physik dot fu-berlin.de
2015-02-21 15:07 ` [Bug target/65153] [SH][4.9 Regression] " olegendo at gcc dot gnu.org
2015-02-21 15:30 ` olegendo at gcc dot gnu.org
2015-02-21 17:07 ` olegendo at gcc dot gnu.org
2015-02-22  5:18 ` kkojima at gcc dot gnu.org
2015-02-22  5:20 ` kkojima at gcc dot gnu.org
2015-02-22 14:48 ` olegendo at gcc dot gnu.org
2015-02-22 23:49 ` olegendo at gcc dot gnu.org
2015-02-23  0:13 ` kkojima at gcc dot gnu.org
2015-02-23  1:19 ` olegendo at gcc dot gnu.org
2015-02-23  8:19 ` kkojima at gcc dot gnu.org
2015-02-23 10:58 ` rguenth at gcc dot gnu.org
2015-02-25  5:45 ` kkojima at gcc dot gnu.org
2015-02-25  6:30 ` kkojima at gcc dot gnu.org
2015-03-07 19: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-65153-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).