public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gert.vervoort@philips.com To: gcc-gnats@gcc.gnu.org Subject: optimization/6842: internal compiler error using MMX intrinsics with optimization Date: Mon, 27 May 2002 23:26:00 -0000 [thread overview] Message-ID: <20020528061603.30172.qmail@sources.redhat.com> (raw) >Number: 6842 >Category: optimization >Synopsis: internal compiler error using MMX intrinsics with optimization >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon May 27 23:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: gert.vervoort@philips.com >Release: gcc 3.1 >Organization: >Environment: vervoort@linux22 [67] > uname -a Linux linux22 2.4.18 #2 SMP Fri Apr 19 16:21:16 CEST 2002 i686 unknown vervoort@linux22 [68] > /cadappl/gcc/3.1/bin/gcc -v Reading specs from /cadappl/gcc/3.1/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs Configured with: /home/hooft/Level/Work/gcc/gcc-3.1/gcc-3.1/configure --prefix=/cadappl/gcc/3.1 --enable-shared --enable-languages=c,c++,f77 Thread model: single gcc version 3.1 >Description: gcc 3.1 gives an internal compiler error when compiling a file with an MMX intrinsic with optimization on. Without optimization the file compiles oke. >How-To-Repeat: vervoort@linux22 [69] > /cadappl/gcc/3.1/bin/gcc -mmmx intrinsic_mmx_add3.c vervoort@linux22 [70] > /cadappl/gcc/3.1/bin/gcc -mmmx -O1 intrinsic_mmx_add3 intrinsic_mmx_add3.c: In function `main': intrinsic_mmx_add3.c:15: Internal compiler error in simplify_gen_subreg, at simplify-rtx.c:2711 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/x-unknown-content-type-c_auto_file; name="intrinsic_mmx_add3.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="intrinsic_mmx_add3.c" I2luY2x1ZGUgPHN0ZGlvLmg+CiNpbmNsdWRlIDxtbWludHJpbi5oPgoKbWFpbigpCnsKICAgIF9f bTY0IGEgPSAweDAxMDIwMzA0MDUwNjA3MDg7CiAgICBfX202NCBiID0gMHgxMDIwMzA0MDUwNjA3 MDgwOwogICAgX19tNjQgYyA9IDB4MDAwMDAwMDAwMDAwMDAwMDsKICAgIAogICAgYyA9IF9tbV9h ZGRzX3B1OChhLGIpOwoKICAgIF9tbV9lbXB0eSgpOwoKICAgICBwcmludGYoIjB4JWxseFxuIiwg Yyk7Cn0K
next reply other threads:[~2002-05-28 6:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-27 23:26 gert.vervoort [this message] 2002-06-20 8:56 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=20020528061603.30172.qmail@sources.redhat.com \ --to=gert.vervoort@philips.com \ --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).