public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "simonb at vmware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/103053] New: Unexpected ".global __divti3" emitted for unsigned 128 bit division Date: Wed, 03 Nov 2021 03:42:08 +0000 [thread overview] Message-ID: <bug-103053-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103053 Bug ID: 103053 Summary: Unexpected ".global __divti3" emitted for unsigned 128 bit division Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: simonb at vmware dot com Target Milestone: --- Created attachment 51725 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51725&action=edit Preprocessed reproducer for the bug When compiling the attached reproducer which contains an unsigned 128 bit divide with any of gcc 7.5.0, 9.3.0, 10.3.0 for x86_64 or gcc 9.3.0 for aarch64 with -O2 it emits a .globl __divti3 even though there is no call to that function. In the x86 asm output for the reproducer, there is: .size bar, .-bar .globl __udivti3 .globl __divti3 <-- bogus .global emission .globl foo ... call __udivti3 This occurs on at least: gcc 7.5.0 target x86_64--netbsd gcc 9.3.0 target x86_64--linux-gnu gcc 10.3.0 targets aarch64--netbsd x86_64--netbsd No ".global __divti3" is emitted with: gcc 6.4.0 target x86_64--linux-gnu
next reply other threads:[~2021-11-03 3:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-03 3:42 simonb at vmware dot com [this message] 2021-11-03 3:48 ` [Bug middle-end/103053] " pinskia at gcc dot gnu.org 2021-11-03 4:23 ` pinskia at gcc dot gnu.org 2021-11-03 9:42 ` jakub at gcc dot gnu.org 2021-11-03 10:26 ` simonb at vmware 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-103053-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).