From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 933723861869; Thu, 14 Dec 2023 22:22:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 933723861869 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1702592569; bh=99vkH5DbNrNIvaMOmjVlcYIagBzAk3hLtrTZ+QMyeTA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=CQjx3O7wsq3kVUHfTHjGBRJ5wwL3Mlfk+V17yFccUMOwTbBRw/KaWaysb729ALneE 0ihHbwtMUxq3E6E6SqCfVddTCzAnzd2UybXtWcg0wZDjpDAZIYHYTxm3J/VKVIeXX+ mr7jMOcyN9ee15778iUJEnHCPR7sD+t1oI+FEWtU= From: "patrick at rivosinc dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1 Date: Thu, 14 Dec 2023 22:22:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: patrick at rivosinc dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED 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: bug_status resolution 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=3D112971 Patrick O'Neill changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from Patrick O'Neill --- (In reply to JuzheZhong from comment #14) > Oh, I just take a look again. It seems that the issue is fixed on the tru= nk ? >=20 > Hi, Patrick. >=20 > https://godbolt.org/z/f1rnsYxf9 >=20 > Could you confirm it ? >=20 > If it is fixed, could you send a patch with the test ? >=20 > Thanks. Yay! Will do - I'm a bit tied up today/tomorrow but I'll figure out what fi= xed it/send a patch when I get the chance=