public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sean@rogue-research.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/61593] New: Support '#pragma mark - foo' (by simply ignoring it without warning) Date: Tue, 24 Jun 2014 15:58:00 -0000 [thread overview] Message-ID: <bug-61593-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61593 Bug ID: 61593 Summary: Support '#pragma mark - foo' (by simply ignoring it without warning) Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sean@rogue-research.com On OS X, it is common to use: #pragma mark - foo to divide source code into sections. This is supported by clang and Apple's old gcc fork. gcc however warns: warning: ignoring #pragma mark [-Wunknown-pragmas] And -Wunknown-pragmas is part of -Wall. I'm aware I could use -Wno-unknown-pragmas, but building clean at -Wall is important. As clang does a lot to be compatible with gcc, I'm hoping gcc can do a little to be compatible with clang here. :) No codegen or anything would be required, just ignore and don't warn when #pragma mark is encountered. Cheers.
next reply other threads:[~2014-06-24 15:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-24 15:58 sean@rogue-research.com [this message] 2019-01-17 4:20 ` [Bug target/61593] Support '#pragma mark - foo' on non-Darwin targets " egallager at gcc dot gnu.org 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-07-23 6:52 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2022-11-04 20:29 ` redi at gcc dot gnu.org 2023-07-07 7:27 ` rguenth 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-61593-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).