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/113437] [14 Regression] gcc.dg/tree-ssa/pr95906.c fails on arm since g:6686e16fda4 Date: Fri, 19 Jan 2024 02:46:43 +0000 [thread overview] Message-ID: <bug-113437-4-Q1cw6uTUir@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113437-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113437 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:1c51d0109a4730827c40c3bbd3a59d459828017e commit r14-8266-g1c51d0109a4730827c40c3bbd3a59d459828017e Author: liuhongt <hongtao.liu@intel.com> Date: Fri Jan 19 09:22:39 2024 +0800 Fix testcase failure on many platforms which don't support vect_int_max. After r14-7124-g6686e16fda4190, the testcase can be optimized to MAX_EXPR if the backends support that. So I adjust the testcase to scan for MAX_EXPR, but it failed many platforms which don't support that. As pinski mentioned, target vect_no_int_min_max is only available under vect directory, so for simplicity, I adjust the testcase to scan either MAX_EXPR or original VEC_COND_EXPR. gcc/testsuite/ChangeLog: PR testsuite/113437 * gcc.dg/tree-ssa/pr95906.c: Scan either MAX_EXPR or VEC_COND_EXPR.
next prev parent reply other threads:[~2024-01-19 2:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-17 9:14 [Bug testsuite/113437] New: " clyon at gcc dot gnu.org 2024-01-17 13:32 ` [Bug testsuite/113437] [14 Regression] " rguenth at gcc dot gnu.org 2024-01-17 13:52 ` ro at gcc dot gnu.org 2024-01-18 0:48 ` liuhongt at gcc dot gnu.org 2024-01-18 0:53 ` pinskia at gcc dot gnu.org 2024-01-18 20:58 ` danglin at gcc dot gnu.org 2024-01-19 1:33 ` liuhongt at gcc dot gnu.org 2024-01-19 2:39 ` hp at gcc dot gnu.org 2024-01-19 2:46 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-19 2:47 ` liuhongt 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-113437-4-Q1cw6uTUir@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).