public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "frank.mehnert at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99508] New: Asm labels declared inside a function are ignored
Date: Wed, 10 Mar 2021 08:22:05 +0000	[thread overview]
Message-ID: <bug-99508-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99508

            Bug ID: 99508
           Summary: Asm labels declared inside a function are ignored
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: frank.mehnert at googlemail dot com
  Target Milestone: ---

This is apparently a gcc-11 regression. Following example:

#include <cstdio>
void foo()
{
  void bar() asm ("bar_assembler");
  extern unsigned buzz asm("buzz_assembler");
  bar();
  printf("%d\n", buzz);
}

Compile this C++ source code with -c and look at the generated symbols with
'objdump -tC'. 

g++-10:
0000000000000000         *UND*  0000000000000000 bar_assembler
0000000000000000         *UND*  0000000000000000 buzz_assembler
0000000000000000         *UND*  0000000000000000 printf

g++-11: (Debian experimental 20210306):
0000000000000000         *UND*  0000000000000000 bar()
0000000000000000         *UND*  0000000000000000 buzz
0000000000000000         *UND*  0000000000000000 printf

g++11 produces the same result as g++10 if 'bar' and 'buzz' are declared
outside foo().

             reply	other threads:[~2021-03-10  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  8:22 frank.mehnert at googlemail dot com [this message]
2021-03-10  8:43 ` [Bug c++/99508] [11 Regression] " rguenth at gcc dot gnu.org
2021-03-10  8:48 ` jakub at gcc dot gnu.org
2021-03-10 13:31 ` nathan at gcc dot gnu.org
2021-03-10 15:51 ` cvs-commit at gcc dot gnu.org
2021-03-10 15:55 ` nathan at gcc dot gnu.org
2021-03-20 10:30 ` frank.mehnert at googlemail dot com

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=bug-99508-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).