public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jyong at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/99872] [11 Regression] optimizations sometimes lead to missing asm prefixes
Date: Tue, 06 Apr 2021 08:27:54 +0000	[thread overview]
Message-ID: <bug-99872-4-8ZSJNRJNZY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99872-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from jyong at gcc dot gnu.org ---
No, its the internal compiler symbols like LC5 and _LC6 generated by GCC
ignoring the underscore prefix setting for the target, causing GAS to emit them
as external undefined symbols. LD fails to find the symbols to satisfy them
upon linking.

32bit Windows PE symbols should come with an underscore prefix, this does not
apply to 64bit Windows code.

  parent reply	other threads:[~2021-04-06  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 17:14 [Bug c/99872] New: " jyong at gcc dot gnu.org
2021-04-06  7:33 ` [Bug c/99872] " rguenth at gcc dot gnu.org
2021-04-06  8:27 ` jyong at gcc dot gnu.org [this message]
2021-04-06 11:09 ` jakub at gcc dot gnu.org
2021-04-06 11:34 ` [Bug target/99872] " jakub at gcc dot gnu.org
2021-04-06 16:27 ` jyong at gcc dot gnu.org
2021-04-06 18:10 ` jyong at gcc dot gnu.org
2021-04-07  7:38 ` jakub at gcc dot gnu.org
2021-04-07 13:52 ` cvs-commit at gcc dot gnu.org
2021-04-07 13:58 ` jakub at gcc dot gnu.org

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-99872-4-8ZSJNRJNZY@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).