public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: optimization/7715: inlining of function with inline assembler causes duplicate assembler lables
@ 2002-08-25 3:55 paolo
0 siblings, 0 replies; 2+ messages in thread
From: paolo @ 2002-08-25 3:55 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, linux_dr, nobody, paolo
Synopsis: inlining of function with inline assembler causes duplicate assembler lables
Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Sat Aug 24 21:26:53 2002
Responsible-Changed-Why:
.
State-Changed-From-To: open->closed
State-Changed-By: paolo
State-Changed-When: Sat Aug 24 21:26:53 2002
State-Changed-Why:
Duplicate of optimization/7714.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7715
^ permalink raw reply [flat|nested] 2+ messages in thread
* optimization/7715: inlining of function with inline assembler causes duplicate assembler lables
@ 2002-08-24 18:06 linux_dr
0 siblings, 0 replies; 2+ messages in thread
From: linux_dr @ 2002-08-24 18:06 UTC (permalink / raw)
To: gcc-gnats
>Number: 7715
>Category: optimization
>Synopsis: inlining of function with inline assembler causes duplicate assembler lables
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Sat Aug 24 18:06:03 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Loren Osborn <linux_dr@yahoo.com>
>Release: gcc 3.1.1
>Organization:
>Environment:
Linux Mandrake 8.1
>Description:
I found a similar bug to PR233, and was disappointed to
see that PR233 was closed, appearantly just because the
URL to the test case became a broken link.
I think I have found a manifistaion of the same bug,
although it doesn't involve unrolling loops. It involves
inlining of functions with inline-assembler lables in it...
I have included a minimal test case
As far as I am aware, the code itself (while not
technically vailid ANSI C, because ANSI C doesn't
explicitly allow inline assembler) should be valid in
gcc.
>How-To-Repeat:
gcc -O3 -c -o InlineLableBug.o InlineLableBug.c
>Fix:
gcc should probably prepend (or append) a string to each assembler label that is unique to each instantiation of that function.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="InlineLableBug.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="InlineLableBug.c"
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-08-25 4:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-08-25 3:55 optimization/7715: inlining of function with inline assembler causes duplicate assembler lables paolo
-- strict thread matches above, loose matches on Subject: below --
2002-08-24 18:06 linux_dr
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).