public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dmc@bayarea.net To: gcc-gnats@gcc.gnu.org Subject: optimization/5442: Internal compiler error if -msse intrinsic used with -O off Date: Sun, 20 Jan 2002 23:46:00 -0000 [thread overview] Message-ID: <20020121073756.20968.qmail@sources.redhat.com> (raw) >Number: 5442 >Category: optimization >Synopsis: Internal compiler error if -msse intrinsic used with -O off >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Sun Jan 20 23:46:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Donald Craig >Release: 3.1 20020120 (experimental) >Organization: >Environment: System: CYGWIN_NT-5.0 DRAGON 1.3.7(0.51/3/2) 2002-01-19 13:20 i686 Athlon XP 1900+ host: i686-pc-cygwin build: i686-pc-cygwin target: i686-pc-cygwin configured with: ../gcc/configure --prefix=/usr/local/bin/gcc3.1 >Description: Compiling fpxor.c without optimization produces: $ gcc -g -msse -o fpxor fpxor.c fpxor.c: In function `main': fpxor.c:12: Internal compiler error in emit_move_insn, at expr.c:2746 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >How-To-Repeat: Compile this code (fpxor.c) without -O: #include <xmmintrin.h> int main( argc, argv ) int argc; char **argv; /* gcc -g -msse -o fpxor fpxor.c */ { static __m128 from1, from2, to; to = _mm_xor_ps( from1, from2 ); exit( 0 ); } >Fix: Compile with -O1 or -O2 or -O3 >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="fpxor.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="fpxor.c" I2luY2x1ZGUgPHhtbWludHJpbi5oPg0KDQppbnQgbWFpbiggYXJnYywgYXJndiApDQppbnQgYXJn YzsNCmNoYXIgKiphcmd2Ow0KLyoNCiAgZ2NjIC1nIC1tYXJjaD1hdGhsb24gLW1zc2UgLW8gZnB4 b3IgZnB4b3IuYw0KKi8NCiAgew0KICAgIHN0YXRpYyBfX20xMjggZnJvbTEsIGZyb20yLCB0bzsN Cg0KICAgIHRvID0gX21tX3hvcl9wcyggZnJvbTEsIGZyb20yICk7DQogICAgZXhpdCggMCApOw0K ICB9DQoNCg==
next reply other threads:[~2002-01-21 7:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-20 23:46 dmc [this message] 2002-05-28 6:04 hubicka
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=20020121073756.20968.qmail@sources.redhat.com \ --to=dmc@bayarea.net \ --cc=gcc-gnats@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: linkBe 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).