public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de To: berndtrog@yahoo.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: inline-asm/10857: Inlining a function with inline-asm: "error: impossible constraint in `asm'" Date: Mon, 19 May 2003 17:53:00 -0000 [thread overview] Message-ID: <20030519175320.11753.qmail@sources.redhat.com> (raw) Synopsis: Inlining a function with inline-asm: "error: impossible constraint in `asm'" State-Changed-From-To: closed->open State-Changed-By: cae State-Changed-When: Mon May 19 17:53:20 2003 State-Changed-Why: Reopened based on submitter's comment. This is rejected by 3.3 at all optimization levels. I still don't think this should compile but previous versions of gcc accepted it. An arch independant example is below. Could someone please clarify if this supposed to compile at e.g. -S -O3? ----------------- cut ------------------------------- #define PORTD 0x12 static void write_byte(unsigned char adr, unsigned char data ) { __asm__ ("blah %0" : : "i" (adr)); } int main(void) { write_byte( PORTD, 4); return 0; } ----------------- cut ------------------------------- Both gcc-3.2 and older versions of gcc-3.4 accepted this if optimization level was high enough. It is rejected by gcc 3.3 nomatter what. Note that __builtin_constant_p (adr) holds for the inlined copy of write_byte. The patch the prevented this from compiling at -O3 went into gcc-3.4 between 20030331 and 20030519. regards Christian http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10857
next reply other threads:[~2003-05-19 17:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 17:53 ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 9:46 Bernd Trog 2003-05-19 16:06 Bernd Trog 2003-05-19 12:23 ehrhardt 2003-05-19 11:16 berndtrog
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=20030519175320.11753.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=berndtrog@yahoo.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).