public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111964] 13.2.1: potential GIMPLE bug in inline assempler
Date: Tue, 24 Oct 2023 21:32:36 +0000 [thread overview]
Message-ID: <bug-111964-4-8QYrRnP7Wx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111964-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111964
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 46820 (and others).
Again the big issue is top-level inline-asm is just broken for LTO really.
Things like PushAllRegistersAndIterateStack in this case should be put into a
.s file.
I see they did that for deps/v8/src/heap/base/asm/arm64/push_registers_masm.S
already too.
*** This bug has been marked as a duplicate of bug 46820 ***
next prev parent reply other threads:[~2023-10-24 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 17:45 [Bug c++/111964] New: " kloczko.tomasz at gmail dot com
2023-10-24 18:00 ` [Bug middle-end/111964] " pinskia at gcc dot gnu.org
2023-10-24 18:09 ` kloczko.tomasz at gmail dot com
2023-10-24 21:32 ` pinskia at gcc dot gnu.org [this message]
2023-10-24 21:32 ` pinskia 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-111964-4-8QYrRnP7Wx@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).