public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Adam Lackorzynski <adam@os.inf.tu-dresden.de> To: jason@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: inline-asm/9570: [3.3/3.4 regression] Assember error with -finline-functions with g++-3.3 Date: Sat, 15 Mar 2003 19:36:00 -0000 [thread overview] Message-ID: <20030315193600.29834.qmail@sources.redhat.com> (raw) The following reply was made to PR inline-asm/9570; it has been noted by GNATS. From: Adam Lackorzynski <adam@os.inf.tu-dresden.de> To: jason@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: inline-asm/9570: [3.3/3.4 regression] Assember error with -finline-functions with g++-3.3 Date: Sat, 15 Mar 2003 20:29:27 +0100 Hi, On Sat Mar 15, 2003 at 17:24:14 -0000, jason@gcc.gnu.org wrote: > Synopsis: [3.3/3.4 regression] Assember error with -finline-functions with g++-3.3 > > State-Changed-From-To: analyzed->closed > State-Changed-By: jason > State-Changed-When: Sat Mar 15 17:24:13 2003 > State-Changed-Why: > This is not a bug. Your code assumes that the inline assembly > will be emitted after the definition of foo(), but if foo() is > inline (as a result of -finline-functions), it is deferred until > EOF, so the inline assembly is emitted after the definition of i. > i lives in .bss, so you end up trying to emit executable code into > .bss, which doesn't work very well. You probably want to wrap > that code in .pushsection ".text" and .popsection > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9570 Just a small annotation: I think the problem is the location of the "b" definition. If I pull the definition of "b" out of the function, the test case compiles. Looking at the asm-code, the place of the definition (or whatever it exactly is) of b differs and if it's below the inline asm code, it doesn't work. --- x.c Sat Mar 15 19:56:23 2003 +++ x2.c Sat Mar 15 19:56:36 2003 @@ -1,7 +1,7 @@ int i = 0; -void foo() { static bool b; +void foo() { if (! i) asm("movl %%esp, %0" : "=r" (i)); } Adding .pushsection and .popsection around the call does seem to fix it as well. Thanks, Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
next reply other threads:[~2003-03-15 19:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-15 19:36 Adam Lackorzynski [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-15 17:24 jason 2003-03-15 17:07 jason 2003-02-24 16:36 Janis Johnson
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=20030315193600.29834.qmail@sources.redhat.com \ --to=adam@os.inf.tu-dresden.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=jason@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).