From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2E0EB386F82E; Tue, 4 Aug 2020 14:38:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E0EB386F82E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1596551881; bh=su+3652XuJ8agjQs6gosIAH3ZueZLMV1dD5ZOZRr5g8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=b0QVuISadlalyXWJHLug2ptps/zV6QBPc+5oeOSbMONq+nTRoC7o1cHx+n987asne nPC/5yLvzueuJoMgp5twzm2G/FTXsKOYJnc5zfVmjwTroRgPHIUInk+xy1q9SIZD/W J6F16HMUdsR3ToKSAr81foXCd27rfxnR1wNOO3pY= From: "matz at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96373] SVE miscompilation on vectorized division loop, leading to FP exception Date: Tue, 04 Aug 2020 14:38:00 +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: 10.2.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: matz at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rsandifo 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2020 14:38:01 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96373 --- Comment #3 from Michael Matz --- (In reply to Richard Biener from comment #2) > which means for non-memory gimple_could_trap_p (stmt) - sth you can > easily check I guess. Just note that _all_ floating point operations, not just divisions, can trap (without fast-math). You never know if the user enabled stops for any of t= he FP exceptions (overflow, underflow, inexact, invalid op, div-by-zero). So,= on SVE that means all FP operations need to use the loop mask. (Of course enabling stops for something like inexact/xflow is silly, so pun= ting on that might be fine)=