From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 87C933858C55; Fri, 7 Oct 2022 20:18:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 87C933858C55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665173916; bh=k85JLXQy+wsYkz/ETqk8lq+SZQpYdPozC26BM2vfJ+s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=l5GBkAZhoC/hogJF2kZbLRNsPuFzcqfYjPV+1gwMK5WoZ9FumMPBPoQKN1r72qxLd iY8AUAMuahlVHFuu6BcuzZFt1GCxmeTTKn6Npbw+A7rwf6lkBQH8iim0cso/edrokd mJPCA5DB2nEXnQuGguybMvunEry+NkImByH7/NUU= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107183] [10/11/12/13 Regression] -fcompare-debug failure (length) with -fsanitize=float-cast-overflow Date: Fri, 07 Oct 2022 20:18:35 +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: compare-debug-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: 10.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component short_desc target_milestone 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=3D107183 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Component|debug |target Summary|-fcompare-debug failure |[10/11/12/13 Regression] |(length) with |-fcompare-debug failure |-fsanitize=3Dfloat-cast-overf |(length) with |low |-fsanitize=3Dfloat-cast-ov= erf | |low Target Milestone|--- |10.5 --- Comment #1 from Andrew Pinski --- I am 99% sure it is a bug in reg-stack.cc which makes this a target issue as x86_64 is one of two targets which use reg-stack for their FP (m68k being t= he other).=