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/104882] [12 Regression] MVE: Wrong code at -O2 since r12-1434-g046a3beb1673bf4a61c131373b6a5e84158e92bf
Date: Fri, 03 Mar 2023 19:10:00 +0000	[thread overview]
Message-ID: <bug-104882-4-XrIMyroi2o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104882-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:220008eafaaed7433b1c18e394279391e885a138

commit r13-6455-g220008eafaaed7433b1c18e394279391e885a138
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Fri Mar 3 15:59:14 2023 -0300

    [PR104882] [arm] require mve hw for mve run test

    The pr104882.c test is an execution test, but arm_v8_1m_mve_ok only
    tests for compile-time support.  Add a requirement for mve hardware.


    for  gcc/testsuite/ChangeLog

            PR target/104882
            * gcc.target/arm/simd/pr104882.c: Require mve hardware.

      parent reply	other threads:[~2023-03-03 19:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 14:18 [Bug target/104882] New: " acoplan at gcc dot gnu.org
2022-03-11 14:21 ` [Bug target/104882] " acoplan at gcc dot gnu.org
2022-03-14  5:39 ` pinskia at gcc dot gnu.org
2022-03-14  7:50 ` rguenth at gcc dot gnu.org
2022-03-16 14:40 ` clyon at gcc dot gnu.org
2022-03-22 14:37 ` clyon at gcc dot gnu.org
2022-03-25 17:27 ` cvs-commit at gcc dot gnu.org
2022-03-25 17:30 ` clyon at gcc dot gnu.org
2023-03-03 19:10 ` cvs-commit at gcc dot gnu.org [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=bug-104882-4-XrIMyroi2o@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).