public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103094] [12 Regression] AAPCS for new partial vector mode types (e.g. V2x8QI) are incorrect.
Date: Wed, 15 Dec 2021 12:19:11 +0000	[thread overview]
Message-ID: <bug-103094-4-olc4mJav86@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103094-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:

https://gcc.gnu.org/g:73c3dacef9a30d7d66918606a97c496c71289f1b

commit r12-5998-g73c3dacef9a30d7d66918606a97c496c71289f1b
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Wed Dec 15 12:19:00 2021 +0000

    aarch64: Don't classify vector pairs as short vectors [PR103094]

    In this PR we were wrongly classifying a pair of 8-byte vectors
    as a 16-byte âshort vectorâ (in the AAPCS64 sense).  As the
    comment in the patch says, this stems from an old condition
    in aarch64_short_vector_p that is too loose, but that would
    be difficult to tighten now.

    We can still do the right thing for the newly-added modes though,
    since there are no backwards compatibility concerns there.

    Co-authored-by: Tamar Christina <tamar.christina@arm.com>

    gcc/
            PR target/103094
            * config/aarch64/aarch64.c (aarch64_short_vector_p): Return false
            for structure modes, rather than ignoring the type in that case.

    gcc/testsuite/
            PR target/103094
            * gcc.target/aarch64/pr103094.c: New test.

  parent reply	other threads:[~2021-12-15 12:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  9:50 [Bug target/103094] New: [12 Regression] Incorrect codegen from AArch64 intrinsics tnfchris at gcc dot gnu.org
2021-11-05  9:50 ` [Bug target/103094] " tnfchris at gcc dot gnu.org
2021-11-05 12:18 ` tnfchris at gcc dot gnu.org
2021-11-05 12:22 ` pinskia at gcc dot gnu.org
2021-11-05 12:29 ` tnfchris at gcc dot gnu.org
2021-11-06  5:50 ` pinskia at gcc dot gnu.org
2021-11-06 22:33 ` [Bug target/103094] [12 Regression] Incorrect codegen from uint8x8x2_t function arguments pinskia at gcc dot gnu.org
2021-12-13  9:12 ` [Bug target/103094] [12 Regression] AAPCS for new partial vector mode types (e.g. V2x8QI) are incorrect tnfchris at gcc dot gnu.org
2021-12-15 12:19 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-15 12:24 ` 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-103094-4-olc4mJav86@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).