From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D45863858C53; Tue, 14 Feb 2023 17:12:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D45863858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1676394750; bh=nnMZZ6mlD+pILyZSpht5yZfza7V8irsupX6cMYOq+ec=; h=From:To:Subject:Date:In-Reply-To:References:From; b=llUiQ5U3iU+S1O3bSniesOBE9Zf1ZzjTlGGVuj+nZK2R+l7cHJSB5rnu9PbflJbCA 0CvIdu1wuCdttMRfXtXEdtyhAcgOAfKipHPEP3uWTgsrozVsekktWF5fiGdrYBCWLp RBZzdBeH3gJT6jb4yZZF+2WUhxc/VOf/hQs/rjj4= From: "amy.mclaughlin at iar dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108673] ICE with -fstack-clash-protection and noreturn attribute on x86_64-w64-mingw32 Date: Tue, 14 Feb 2023 17:12:30 +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: X-Bugzilla-Severity: normal X-Bugzilla-Who: amy.mclaughlin at iar dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: cc 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=3D108673 amy.mclaughlin at iar dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amy.mclaughlin at iar dot = com --- Comment #3 from amy.mclaughlin at iar dot com --- Regarding Comment 1, the bug in Cygwin's gcc (11.3.0) can't be worked around with `-fno-ipa-pure-const`. The workaround also fails for the msys2 msys bu= ild of gcc (also 11.3.0) but succeeds for the mingw64 build. So I suspect that the bug reproduced with x86_64-pc-cygwin-gcc may not be t= he same bug as the one in this report, despite the similar symptoms.=