From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9787 invoked by alias); 24 Jun 2014 15:58:09 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 9768 invoked by uid 48); 24 Jun 2014 15:58:05 -0000 From: "sean@rogue-research.com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sean@rogue-research.com X-Bugzilla-Status: UNCONFIRMED 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 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-06/txt/msg01879.txt.bz2 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.