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 testsuite/114842] rs6000: Adjust some test cases with powerpc_vsx_ok
Date: Tue, 21 May 2024 02:03:56 +0000	[thread overview]
Message-ID: <bug-114842-4-9Lui9ZFkef@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114842-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:95080f2a40c5dfc098b75029c30380ecf03875dc

commit r15-715-g95080f2a40c5dfc098b75029c30380ecf03875dc
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Mon May 20 21:01:08 2024 -0500

    testsuite, rs6000: Make powerpc_vsx consider current_compiler_flags
[PR114842]

    As noted in PR114842, most of the test cases which require
    effective target check powerpc_vsx_ok actually care about
    if VSX feature is enabled, and they should adopt effective
    target powerpc_vsx instead.  By considering we already have
    a number of test cases having explicit -mvsx in dg-options
    etc., to keep them still be tested as before even without
    vsx enabled by default, this patch is to make powerpc_vsx
    consider current_compiler_flags.

            PR testsuite/114842

    gcc/testsuite/ChangeLog:

            * lib/target-supports.exp (check_effective_target_powerpc_vsx):
Take
            current_compiler_flags into account.

  parent reply	other threads:[~2024-05-21  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  6:18 [Bug testsuite/114842] New: " linkw at gcc dot gnu.org
2024-04-25  6:19 ` [Bug testsuite/114842] " linkw at gcc dot gnu.org
2024-04-25  6:24 ` linkw at gcc dot gnu.org
2024-05-21  2:03 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-21  2:04 ` cvs-commit at gcc dot gnu.org
2024-05-29  2:42 ` cvs-commit at gcc dot gnu.org
2024-06-18  2:48 ` cvs-commit 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-114842-4-9Lui9ZFkef@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).