public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/114842] New: rs6000: Adjust some test cases with powerpc_vsx_ok Date: Thu, 25 Apr 2024 06:18:59 +0000 [thread overview] Message-ID: <bug-114842-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114842 Bug ID: 114842 Summary: rs6000: Adjust some test cases with powerpc_vsx_ok Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: linkw at gcc dot gnu.org Target Milestone: --- The current effective target powerpc_vsx_ok is mainly to check if it's fine to specify -mvsx (without any warnings etc.) and can finally result in a object file (it means the underlying environment like assembler supports vsx insns). But most of the test cases being guarded with this checking actually want to check if VSX feature is enabled, such as: the wanted behavior only happens with VSX feature enabled. When users specifying -mno-vsx in RUNTESTFLAGS, it can disable VSX feature (with some old runtest, -mno-vsx comes after -mvsx), but powerpc_vsx_ok checking will still pass as it's fine to specify -mvsx, so if the test case doesn't have explicit -mvsx, then the given -mno-vsx can disable VSX feature and make that test case fail, meanwhile even if the test case has specified -mvsx explicitly it would fail with old runtest as -mno-vsx comes last. We already have another effective target powerpc_vsx which effectively checks for VSX enabled, so we should update most of test case to adopt it instead.
next reply other threads:[~2024-04-25 6:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-25 6:18 linkw at gcc dot gnu.org [this message] 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 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@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: linkBe 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).