From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D95613939C38; Wed, 24 Jun 2020 08:56:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D95613939C38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1592989008; bh=k08RqVhzo+tcvj+yYn8mR13Lc5Wk3vONMuFUtp9Kv7s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SqmYYJ/b3lHvqGlk//jwHop0ZQPeCPayrEmUjLhsWOaKPUeWDhwIF4+YoClYG2kC5 rwmLnkDFX8I8o5J2BBVj4MOU68/fqCHPmjLKwhVJkf7ed+wOo4XHR7slwA9rfAQIho DZm+vwBdnW6x/Hx8ZTvSGyq1sJzioHqpdCsBFtI0= From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/92860] [8/9/10/11 regression] Global flags affected by -O settings are clobbered by optimize attribute Date: Wed, 24 Jun 2020 08:56:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: deferred X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.2 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: Wed, 24 Jun 2020 08:56:49 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D92860 --- Comment #30 from Martin Li=C5=A1ka --- (In reply to David Binderman from comment #29) > Maybe I've been slightly less than clear, but to quote myself: > >anything I do to reduce the problem makes it go away Ah, ok! >=20 > So I can't provide a small test case, or output from -E, for this. >=20 > I suggest I wait until the rest of the bug is solved, retest > and go from there. >=20 > My apologies for the lack of clarity. What's the project where you see the issue?=