From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E597E398B875; Sat, 17 Apr 2021 11:17:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E597E398B875 From: "rsandifo at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/100130] New: R section flag handling doesn't cope with intervening decls Date: Sat, 17 Apr 2021 11:17:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rsandifo 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: Sat, 17 Apr 2021 11:17:27 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100130 Bug ID: 100130 Summary: R section flag handling doesn't cope with intervening decls Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: rsandifo at gcc dot gnu.org Target Milestone: --- c-c++-common/attr-retain-7.c checks that we warn for: int __attribute__((used,retain,section(".data.foo"))) foo2 =3D 2; int __attribute__((section(".data.foo"))) foo1 =3D 1; It also makes sure that we output two .section directives, one with the R flag for foo2 and once without for foo1. But this is all keyed on whether we try to =E2=80=9Cswitch=E2=80=9D to the = same section. It therefore doesn't work if there's an intervening decl, such as: int __attribute__((used,retain,section(".data.foo"))) foo2 =3D 2; int between =3D 1; int __attribute__((section(".data.foo"))) foo1 =3D 1; (-fno-toplevel-reorder should ensure this fails, but it fails for me without as well.) This also doesn't work for -fsection-anchors, which is what made me look at it originally. I guess that's a separate bug, but I think it affects how this PR should be fixed.=