From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 298C13857379; Thu, 20 Oct 2022 03:30:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 298C13857379 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666236644; bh=mn9bGzjHu0besBsqC47EneOMmaV8NamUKVpXA39htC0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RmewMqj7tQ86LMrcRf/Ap/4VK99cXx8KGqpC9EqxgOPqZiHaMIM1f6ZofRgFv8pjr FLBwWkysmIZmW2fGNI14fWvv5jWamGwUoQY+DfbHSaj+hK99sYU+Kqfsp25XqYqxep ozwpEiSQyd3bUosYTjzzSt+6YJRPBNebMfdD49R0= From: "crazylht at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107261] ICE: in classify_argument, at config/i386/i386.cc:2523 on __bf16 vect argument or return value Date: Thu, 20 Oct 2022 03:30:43 +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: 13.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: crazylht at gmail dot com X-Bugzilla-Status: NEW 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=3D107261 --- Comment #4 from Hongtao.liu --- (In reply to Hongtao.liu from comment #3) > (In reply to Jakub Jelinek from comment #2) > > I think: > > --- gcc/config/i386/i386.cc.jj 2022-10-14 09:35:56.158990825 +0200 > > +++ gcc/config/i386/i386.cc 2022-10-19 19:49:07.883101047 +0200 > > @@ -2507,6 +2507,7 @@ classify_argument (machine_mode mode, co > > case E_V2SImode: > > case E_V4HImode: > > case E_V4HFmode: > > + case E_V4BFmode: > > case E_V2HFmode: > > case E_V8QImode: > > classes[0] =3D X86_64_SSE_CLASS; > > ought to fix this. >=20 > We haven't support V4BFmode yet, why there's V4BFmode coming in. > We'll take a look. It's ok for 32-bit vector bf, but ICE for 64-bit vector. typedef __bf16 __attribute__((__vector_size__ (4))) V; V foo (V v, V a) { return v + a; }=