public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview] Message-ID: <bug-100130-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100130 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 = 2; int __attribute__((section(".data.foo"))) foo1 = 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 “switch” 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 = 2; int between = 1; int __attribute__((section(".data.foo"))) foo1 = 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.
next reply other threads:[~2021-04-17 11:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-17 11:17 rsandifo at gcc dot gnu.org [this message] 2021-04-17 11:27 ` [Bug middle-end/100130] " rsandifo at gcc dot gnu.org 2021-04-21 8:08 ` cvs-commit at gcc dot gnu.org 2021-04-21 8:10 ` rsandifo at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-100130-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).