public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/96882] Wrong assembly code generated with arm-none-eabi-gcc -flto -mfloat-abi=hard options Date: Tue, 01 Sep 2020 15:00:17 +0000 [thread overview] Message-ID: <bug-96882-4-9yUw1g5SQk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96882-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96882 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- LTO seems to be getting confused as to the ABI. Investigating... In the mean time, the only work-around I can think of is to remove -flto from your build.
next prev parent reply other threads:[~2020-09-01 15:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-01 12:57 [Bug c/96882] New: " emilie.feral at numworks dot com 2020-09-01 13:25 ` [Bug c/96882] " rearnsha at gcc dot gnu.org 2020-09-01 13:43 ` emilie.feral at numworks dot com 2020-09-01 15:00 ` rearnsha at gcc dot gnu.org [this message] 2020-09-01 19:36 ` [Bug target/96882] " rearnsha at gcc dot gnu.org 2020-09-02 8:10 ` emilie.feral at numworks dot com 2020-09-02 10:05 ` rearnsha at gcc dot gnu.org 2020-09-15 9:32 ` emilie.feral at numworks dot com 2020-09-15 13:36 ` rearnsha at gcc dot gnu.org 2022-03-14 15:36 ` dcrocker at eschertech dot com 2022-03-29 16:05 ` cvs-commit at gcc dot gnu.org 2023-04-11 17:18 ` dcrocker at eschertech 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-96882-4-9yUw1g5SQk@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).