public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111828] rs6000: Parse inline asm string to figure out it requires HTM feature or not.
Date: Tue, 17 Oct 2023 02:42:36 +0000 [thread overview]
Message-ID: <bug-111828-4-SwqWXSlI21@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111828-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111828
--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #1)
> If the user compiles a piece of inline asm that doesn't support the
> features used in that inline asm, then that is user error!
I meant to say: If the user compiles a piece of inline asm using options that
doesn't support the features used in that inline asm, then that is user error!
next prev parent reply other threads:[~2023-10-17 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 3:40 [Bug target/111828] New: " linkw at gcc dot gnu.org
2023-10-17 2:39 ` [Bug target/111828] " bergner at gcc dot gnu.org
2023-10-17 2:42 ` bergner at gcc dot gnu.org [this message]
2023-10-17 3:29 ` linkw at gcc dot gnu.org
2023-10-17 5:47 ` jan.wassenberg at gmail dot com
2023-10-17 23:31 ` bergner at gcc dot gnu.org
2023-10-17 23:49 ` bergner at gcc dot gnu.org
2023-10-18 0:00 ` bergner at gcc dot gnu.org
2023-10-18 2:29 ` linkw at gcc dot gnu.org
2023-10-24 3:33 ` linkw at gcc dot gnu.org
2023-10-26 8:02 ` linkw at gcc dot gnu.org
2023-11-06 6:15 ` cvs-commit at gcc dot gnu.org
2023-11-15 9:26 ` [Bug target/111828] rs6000: Aggressive inline callee with inline asm without complains from assemblers cvs-commit at gcc dot gnu.org
2023-11-15 9:27 ` cvs-commit at gcc dot gnu.org
2023-11-15 9:29 ` linkw 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-111828-4-SwqWXSlI21@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).