public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pavenis@latnet.lv To: gcc-gnats@gcc.gnu.org Subject: c/4869: ICE on inline assembler Date: Fri, 02 Nov 2001 07:22:00 -0000 [thread overview] Message-ID: <20011113173600.27695.qmail@sourceware.cygnus.com> (raw) >Number: 4869 >Category: c >Synopsis: ICE on inline assembler >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Tue Nov 13 09:46:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Andris Pavenis >Release: gcc-3.1 20011112 (experimental), gcc-3.1 20011030 (experimantal) >Organization: >Environment: i686-pc-linux-gnu: gcc-3.1 20011112 i586-pc-msdosdjgpp: gcc-3.1 20011030 >Description: gcc-3.1 (specified versions) generates ICE on following code which violates aliasing rules. The behaviour of code is undefined, but it should compile. /* This example causes ICE with gcc-3.1 20011030 */ long long rdtsc (void) { long long Result; __asm__ ( " rdtsc\n" : "=ax" ( ((unsigned long *) & Result)[0] ), "=dx" ( ((unsigned long *) & Result)[1] ) ); return Result; } I'm getting following output from ./xgcc -B./ -c bad.c bad1.c: In function `rdtsc': bad1.c:11: Internal compiler error in fixup_var_refs_1, at function.c:1912 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. Andris >How-To-Repeat: gcc -c bad1.c >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-11-13 17:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011113173600.27695.qmail@sourceware.cygnus.com \ --to=pavenis@latnet.lv \ --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).