public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: linux_dr@yahoo.com To: gcc-gnats@gcc.gnu.org Subject: optimization/7714: inlining of function with inline assembler causes duplicate assembler lables Date: Sat, 24 Aug 2002 18:06:00 -0000 [thread overview] Message-ID: <20020824231217.29207.qmail@sources.redhat.com> (raw) >Number: 7714 >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"
next reply other threads:[~2002-08-25 1:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-24 18:06 linux_dr [this message] 2002-12-06 13:09 bangerth
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=20020824231217.29207.qmail@sources.redhat.com \ --to=linux_dr@yahoo.com \ --cc=gcc-gnats@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).