public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bernd Trog <berndtrog@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: inline-asm/10857: Inlining a function with inline-asm: "error: impossible constraint in `asm'" Date: Wed, 21 May 2003 09:46:00 -0000 [thread overview] Message-ID: <20030521094601.23064.qmail@sources.redhat.com> (raw) The following reply was made to PR inline-asm/10857; it has been noted by GNATS. From: Bernd Trog <berndtrog@yahoo.com> To: jh@suse.cz, ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: inline-asm/10857: Inlining a function with inline-asm: "error: impossible constraint in `asm'" Date: Wed, 21 May 2003 02:38:42 -0700 (PDT) --- ehrhardt@mathematik.uni-ulm.de wrote: > The patch the prevented this from compiling at -O3 went into gcc-3.4 > between 20030331 and 20030519. After spending some CPU cycles on compiling gcc, it looks like: +Fri Apr 11 00:12:14 CEST 2003 Jan Hubicka <jh@suse.cz> + + PR inline-asm/8803 + * function.c (instantate_virtual_regs): Verify that all ASM statements + match after the virutal regs instantiation. + gcc/gcc/function.c: instantiate_virtual_regs_1 (&CALL_INSN_FUNCTION_USAGE (insn), NULL_RTX, 0); + + /* Past this point all ASM statements should match. Verify that + to avoid failures later in the compilation process. */ + if (asm_noperands (PATTERN (insn)) >= 0 + && ! check_asm_operands (PATTERN (insn))) + instantiate_virtual_regs_lossage (insn); } triggered my regression. Removing that patch from 3.3.0 makes my code compile again - I'm happy :-) Maybe its possible to add another condition to that if statement? __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
next reply other threads:[~2003-05-21 9:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-21 9:46 Bernd Trog [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 17:53 ehrhardt 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=20030521094601.23064.qmail@sources.redhat.com \ --to=berndtrog@yahoo.com \ --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).