From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: "Kewen.Lin" <linkw@linux.ibm.com>,
dje.gcc@gmail.com, linkw@gcc.gnu.org, bergner@linux.ibm.com,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] report message for operator %a on unaddressible exp
Date: Thu, 16 May 2024 09:55:51 -0500 [thread overview]
Message-ID: <20240516145551.GJ19790@gate.crashing.org> (raw)
In-Reply-To: <h48bk568csu.fsf@genoa.aus.stglabs.ibm.com>
Hi!
On Thu, May 16, 2024 at 02:56:49PM +0800, Jiufu Guo wrote:
> Jiufu Guo <guojiufu@linux.ibm.com> writes:
> > Segher Boessenkool <segher@kernel.crashing.org> writes:
> >> On Tue, May 14, 2024 at 05:53:56PM +0800, Jiufu Guo wrote:
> >>> Thanks so much for your great review!
> >>> Reference other messages, I'm wondering "invalid %%a value" may be
> >>> acceptable, or "invalid %%a address expression in TOC" maybe better.
> >>
> >> "%%a requires a memory operand"? Maybe even print out the actual
> >> operand given, too.
> >
> > Thanks! I updated the code using:
> > "%%a requires a memory reference operand", since the actual operand
> > is treated as the address.
>
> I suspect one thing here: if "%%a requires memory" is accurate vs.
> "%%a requires a memory reference".
>
> Reference the words from doc:
> https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Generic-Operand-Modifiers
> a: Substitute a memory reference, with the actual operand treated as the
> address.
>
> And for below code:
> '("#%a0" : :"m"(x))' is not accepted.
Yeah, it always confuses me. Sorry. The operand is the actual address.
> While '("#%a0" : :"r"(&x))' is ok.
>
> So, it may be more accurate that: "%%a" as requirement of address of
> memory.
That sounds good yes.
Segher
next prev parent reply other threads:[~2024-05-16 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 2:57 Jiufu Guo
2024-05-13 6:27 ` Kewen.Lin
2024-05-14 3:00 ` Jiufu Guo
2024-05-14 3:15 ` Kewen.Lin
2024-05-14 3:32 ` Jiufu Guo
2024-05-14 9:11 ` Segher Boessenkool
2024-05-14 9:40 ` Jiufu Guo
2024-05-14 9:20 ` Segher Boessenkool
2024-05-14 9:53 ` Jiufu Guo
2024-05-14 10:43 ` Segher Boessenkool
2024-05-15 2:34 ` Jiufu Guo
2024-05-16 6:56 ` Jiufu Guo
2024-05-16 14:55 ` Segher Boessenkool [this message]
2024-05-13 11:03 ` Segher Boessenkool
2024-05-14 2:49 ` Jiufu Guo
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=20240516145551.GJ19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
/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).