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] New: [11 Regression] optimizations sometimes lead to missing asm prefixes Date: Thu, 01 Apr 2021 17:14:13 +0000 [thread overview] Message-ID: <bug-99872-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99872 Bug ID: 99872 Summary: [11 Regression] optimizations sometimes lead to missing asm prefixes Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jyong at gcc dot gnu.org Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-w64-mingw32 Build: x86_64-pc-linux-gnu Created attachment 50497 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50497&action=edit lib32_libmingwex_a-pow.c test case Compiling with the following command line: x86_64-w64-mingw32-gcc -O2 -c lib32_libmingwex_a-pow.c -std=gnu99 -m32 Causes an undefined symbols with the wrong asm prefixes to be emitted: 00000000 T ___attribute__pow 00000010 B ___attribute__pow_d 00000008 B ___attribute__pow_x 00000000 B ___attribute__pow_y 00000000 b .bss 00000000 d .data U ___fpclassify U _internal_modf U LC5 U _LC6 00000000 r .rdata 00000000 r .rdata$zzz U ___signbit 00000000 t .text Adding -fno-leading-underscore makes the symbols resolved, 32bit Windows code is supposed to have a leading underscore.
next reply other threads:[~2021-04-01 17:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 17:14 jyong at gcc dot gnu.org [this message] 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 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@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: 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).