public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc-oren@ben-kiki.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64117] New: warning control #pragmas in precompiled headers are not obeyed for template code
Date: Sat, 29 Nov 2014 15:52:00 -0000	[thread overview]
Message-ID: <bug-64117-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64117

            Bug ID: 64117
           Summary: warning control #pragmas in precompiled headers are
                    not obeyed for template code
           Product: gcc
           Version: 4.8.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gcc-oren@ben-kiki.org

Created attachment 34140
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34140&action=edit
A header file, a source file, and a RUNME script using them to demonstrate the
problem.

Temporarily disabling warnings surrounding template code works fine, except
when included in a precompiled header. Then, the warnings remain in effect, and
are triggered in any C++ code that uses the template.

In my project, this means I just can't use precompiled headers. We are missing
out on cutting down our build time as a result.

BTW, speaking of precompiled headers, it sucks that `#pragma once` is not
allowed when precompiling a header file ("#pragma once in main file"), but
that's a minor annoyance - one can switch back to the bad old days of guard
macros.


             reply	other threads:[~2014-11-29 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 15:52 gcc-oren@ben-kiki.org [this message]
2014-12-19 13:11 ` [Bug c++/64117] " gcc-oren@ben-kiki.org
2015-08-23 14:16 ` gcc-oren@ben-kiki.org
2015-08-23 15:33 ` [Bug pch/64117] " manu at gcc dot gnu.org
2020-06-24 12:30 ` fsmoke at mail dot ru
2021-02-25 11:32 ` chihchengyuan at gmail dot com
2021-06-14 19:02 ` colomar.6.4.3 at gmail dot com
2021-06-14 19:04 ` colomar.6.4.3 at gmail dot com
2023-11-08  3:24 ` lhyatt at gcc dot gnu.org
2023-11-28 17:12 ` lhyatt 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-64117-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: link
Be 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).