public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47540] New: ARM THUMB crash with complex numbers
Date: Sun, 30 Jan 2011 09:44:00 -0000 [thread overview]
Message-ID: <bug-47540-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47540
Summary: ARM THUMB crash with complex numbers
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ian@airs.com
When I compile this C code with -O2 -mthumb on a current mainline compiler
configured for arm-rtems4.11, it crashes.
extern double f1 (_Complex double);
extern _Complex double f2 (_Complex double);
_Complex double f (_Complex double x) { return f1 (x) == 0 ? 0 : f2 (x); }
> gcc/xgcc -Bgcc/ -c -O2 -mthumb foo.c
foo.c: In function 'f':
foo.c:3:1: internal compiler error: in find_valid_class, at reload.c:710
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
The error is the gcc_assert at the end of find_valid_class.
This code compiles OK on x86 and on ARM when not using -mthumb.
next reply other threads:[~2011-01-30 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 9:44 ian at airs dot com [this message]
2011-01-30 10:24 ` [Bug target/47540] " ian at airs dot com
2011-01-30 13:34 ` mikpe at it dot uu.se
2011-01-30 17:50 ` joel at gcc dot gnu.org
2011-01-31 10:50 ` mikpe at it dot uu.se
2011-01-31 19:04 ` ian at airs dot com
2011-02-01 10:12 ` mikpe at it dot uu.se
2011-02-01 10:25 ` rearnsha at gcc dot gnu.org
2011-02-28 4:17 ` ramana at gcc dot gnu.org
2011-03-25 20:10 ` jakub at gcc dot gnu.org
2011-04-28 16:51 ` rguenth at gcc dot gnu.org
2013-07-10 10:59 ` sebastian.huber@embedded-brains.de
2015-01-02 20:53 ` joel 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-47540-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).