public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/11442] [3.3 regression] [arm] invalid assembler on arm Date: Wed, 01 Oct 2003 09:15:00 -0000 [thread overview] Message-ID: <20031001091518.23190.qmail@sources.redhat.com> (raw) In-Reply-To: <20030706115750.11442.debian-gcc@lists.debian.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11442 rearnsha at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From rearnsha at gcc dot gnu dot org 2003-10-01 09:15 ------- Not a bug. Your source code is invalid. You can't put any "asm" in your source code that requires more than 4 bytes per statement. You have ".skip 16" operations which are violating this constraint and consequently gcc gets confused in a way which can only be detected by the assembler. The compiler does not parse the body of asm statements to divine their meaning.
next prev parent reply other threads:[~2003-10-01 9:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-06 11:57 [Bug target/11442] New: " debian-gcc at lists dot debian dot org 2003-07-06 11:58 ` [Bug target/11442] " debian-gcc at lists dot debian dot org 2003-07-09 22:19 ` dhazeghi at yahoo dot com 2003-08-23 0:44 ` dhazeghi at yahoo dot com 2003-10-01 9:15 ` rearnsha at gcc dot gnu dot org [this message] 2003-10-01 9:18 ` rearnsha at gcc dot gnu dot org 2003-10-01 9:29 ` falk dot hueffner at student dot uni-tuebingen dot de 2003-10-01 10:16 ` rearnsha at gcc dot gnu dot 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=20031001091518.23190.qmail@sources.redhat.com \ --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: 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).