public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114607] New: aarch64: Incorrect expansion of svsudot
Date: Fri, 05 Apr 2024 16:14:52 +0000	[thread overview]
Message-ID: <bug-114607-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114607

            Bug ID: 114607
           Summary: aarch64: Incorrect expansion of svsudot
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rsandifo at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64*-*-*

svsudot is supposed to expand to USDOT with the second and third arguments
swapped.  However, there is a thinko in the code that does the reversal, making
it a no-op.  Unfortunately, the tests simply accept the buggy form. :-(

For example, gcc.target/aarch64/sve/acle/asm/sudot_s32.c contains:

/*
** sudot_s32_tied1:
**      usdot   z0\.s, z2\.b, z4\.b
**      ret
*/
TEST_TRIPLE_Z (sudot_s32_tied1, svint32_t, svint8_t, svuint8_t,
               z0 = svsudot_s32 (z0, z2, z4),
               z0 = svsudot (z0, z2, z4))

where the usdot z2 and z4 operands should be in the opposite order.

             reply	other threads:[~2024-04-05 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 16:14 rsandifo at gcc dot gnu.org [this message]
2024-04-05 16:15 ` [Bug target/114607] " rsandifo at gcc dot gnu.org
2024-04-08 15:53 ` cvs-commit at gcc dot gnu.org
2024-04-08 15:59 ` rsandifo at gcc dot gnu.org
2024-07-31 11:48 ` ktkachov at gcc dot gnu.org
2024-08-16  6:58 ` cvs-commit at gcc dot gnu.org
2024-08-16 14:38 ` cvs-commit at gcc dot gnu.org
2024-08-16 14:41 ` rsandifo 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-114607-4@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).