From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: David Faust <david.faust@oracle.com>
Cc: gcc-patches@gcc.gnu.org, cupertino.miranda@oracle.com
Subject: Re: [PATCH] bpf: correct pseudo-C template for add3 and sub3
Date: Thu, 27 Jul 2023 20:50:30 +0200 [thread overview]
Message-ID: <87ila51955.fsf@oracle.com> (raw)
In-Reply-To: <20230727181105.15595-1-david.faust@oracle.com> (David Faust's message of "Thu, 27 Jul 2023 11:11:05 -0700")
> The pseudo-C output templates for these instructions were incorrectly
> using operand 1 rather than operand 2 on the RHS, which led to some
> very incorrect assembly generation with -masm=pseudoc.
>
> Tested on bpf-unknown-none.
> OK?
OK. Thanks for spotting and fixing this!
>
> gcc/
>
> * config/bpf/bpf.md (add<AM:mode>3): Use %w2 instead of %w1
> in pseudo-C dialect output template.
> (sub<AM:mode>3): Likewise.
>
> gcc/testsuite/
>
> * gcc.target/bpf/alu-2.c: New test.
> * gcc.target/bpf/alu-pseudoc-2.c: Likewise.
> ---
> gcc/config/bpf/bpf.md | 4 ++--
> gcc/testsuite/gcc.target/bpf/alu-2.c | 12 ++++++++++++
> gcc/testsuite/gcc.target/bpf/alu-pseudoc-2.c | 13 +++++++++++++
> 3 files changed, 27 insertions(+), 2 deletions(-)
> create mode 100644 gcc/testsuite/gcc.target/bpf/alu-2.c
> create mode 100644 gcc/testsuite/gcc.target/bpf/alu-pseudoc-2.c
>
> diff --git a/gcc/config/bpf/bpf.md b/gcc/config/bpf/bpf.md
> index 2ffc4ebd17e..66436397bb7 100644
> --- a/gcc/config/bpf/bpf.md
> +++ b/gcc/config/bpf/bpf.md
> @@ -131,7 +131,7 @@ (define_insn "add<AM:mode>3"
> (plus:AM (match_operand:AM 1 "register_operand" " 0,0")
> (match_operand:AM 2 "reg_or_imm_operand" " r,I")))]
> "1"
> - "{add<msuffix>\t%0,%2|%w0 += %w1}"
> + "{add<msuffix>\t%0,%2|%w0 += %w2}"
> [(set_attr "type" "<mtype>")])
>
> ;;; Subtraction
> @@ -144,7 +144,7 @@ (define_insn "sub<AM:mode>3"
> (minus:AM (match_operand:AM 1 "register_operand" " 0")
> (match_operand:AM 2 "register_operand" " r")))]
> ""
> - "{sub<msuffix>\t%0,%2|%w0 -= %w1}"
> + "{sub<msuffix>\t%0,%2|%w0 -= %w2}"
> [(set_attr "type" "<mtype>")])
>
> ;;; Negation
> diff --git a/gcc/testsuite/gcc.target/bpf/alu-2.c b/gcc/testsuite/gcc.target/bpf/alu-2.c
> new file mode 100644
> index 00000000000..0444a9bc68a
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/bpf/alu-2.c
> @@ -0,0 +1,12 @@
> +/* Check add and sub instructions. */
> +/* { dg-do compile } */
> +/* { dg-options "" } */
> +
> +long foo (long x, long y)
> +{
> + return y - x + 4;
> +}
> +
> +/* { dg-final { scan-assembler-not {sub\t(%r.),\1\n} } } */
> +/* { dg-final { scan-assembler {sub\t(\%r.),(\%r.)\n} } } */
> +/* { dg-final { scan-assembler {add\t(\%r.),4\n} } } */
> diff --git a/gcc/testsuite/gcc.target/bpf/alu-pseudoc-2.c b/gcc/testsuite/gcc.target/bpf/alu-pseudoc-2.c
> new file mode 100644
> index 00000000000..751db2477c0
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/bpf/alu-pseudoc-2.c
> @@ -0,0 +1,13 @@
> +/* Check add and sub instructions (pseudoc asm dialect). */
> +/* { dg-do compile } */
> +/* { dg-options "-masm=pseudoc" } */
> +
> +long foo (long x, long y)
> +{
> + return y - x + 4;
> +}
> +
> +/* { dg-final { scan-assembler-not {\t(r.) -= \1\n} } } */
> +/* { dg-final { scan-assembler {\t(r.) -= (r.)\n} } } */
> +/* { dg-final { scan-assembler {\t(r.) \+= 4\n} } } */
> +
prev parent reply other threads:[~2023-07-27 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:11 David Faust
2023-07-27 18:50 ` Jose E. Marchesi [this message]
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=87ila51955.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=gcc-patches@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).