public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55381] [4.8 Regression]: build fails on cris-elf building libgfortran with host-gcc-4.4, ICE compiling matmul_i1.c
Date: Sun, 18 Nov 2012 20:17:00 -0000 [thread overview]
Message-ID: <bug-55381-4-qZhHmIMjEN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55381-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55381
--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-11-18 20:17:24 UTC ---
(In reply to comment #2)
> (In reply to comment #0)
> > /tmp/hpautotest-gcc0/gcc/libgfortran/generated/matmul_i1.c:79:1: internal
> > compiler error: Illegal instruction
>
> Not observed with gcc-4.7.2-2.fc17.x86_64.
But does happen with "gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)" as well as
"gcc version 4.4.5 (Debian 4.4.5-8)".
And those are the gcc versions I have at an arm-length. There's more at CFarm,
but IIRC most of them are gcc-4.4 era and earlier.
Maybe there's some -fpermissive or -fno-strict-aliasing combo to stick there.
I don't really like the thought of raising the minimum gcc version already...
next prev parent reply other threads:[~2012-11-18 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 16:53 [Bug middle-end/55381] New: " hp at gcc dot gnu.org
2012-11-18 17:04 ` [Bug middle-end/55381] " hp at gcc dot gnu.org
2012-11-18 19:48 ` hp at gcc dot gnu.org
2012-11-18 20:17 ` hp at gcc dot gnu.org [this message]
2012-11-19 5:46 ` venkataramanan.kumar at amd dot com
2012-11-19 17:50 ` pthaugen at gcc dot gnu.org
2012-11-19 22:08 ` bergner at gcc dot gnu.org
2012-11-20 13:02 ` schwab@linux-m68k.org
2012-11-20 16:51 ` dnovillo at gcc dot gnu.org
2012-11-20 18:12 ` hp at gcc dot gnu.org
2012-11-25 15:55 ` rguenth at gcc dot gnu.org
2012-11-25 21:01 ` hp 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-55381-4-qZhHmIMjEN@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).