From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B86E23858D39; Thu, 2 Nov 2023 18:46:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B86E23858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698950793; bh=KKiiDi+2a5uZvqhuiwnBzXRAkb7bHfiPEV5wAsq1Bz0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vrlB+tXDdD23UTZ4TxrIMXMntcEnRdStRXBtNT+fBv0/oUloUGFT+QAY9jES0WXzm 7AIpt5wdpLX3a2IYmSKNs0mWLpW/s0v9rfoIvxeKYtrcZ9jh32eglvtHXGpVAvcKz8 9coVqjjtujgBoOM8fueleHKGTlpwPGufhm0DL544= From: "rdapp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111311] RISC-V regression testsuite errors with --param=riscv-autovec-preference=scalable Date: Thu, 02 Nov 2023 18:46:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: rdapp at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111311 --- Comment #10 from Robin Dapp --- As a general remark: Some of those are present on other backends as well, = some have been introduced by recent common-code changes and some are bogus test prerequisites or checks. I'm not saying we are in perfect shape but we have several months to deal with most of those - if there is a high-severity bug= we can of course still do common code changes if necessary, although the bar w= ill be higher. FYI 5ish of the mentioned bugs will be gone with the slp-reduc-7.c fix but = it will introduce another backend missed optimization - at first this might ap= pear worse (just by numbers) but it actually isn't. Once stage 1 is over I'm go= ing to focus on the Fortran tests as well as the signbit execution tests (in ca= se they are still there at that time).=