public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/48839] #error should terminate compilation - similar to missing #include
Date: Thu, 23 Feb 2023 20:38:28 +0000	[thread overview]
Message-ID: <bug-48839-4-pGNmii8e2j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48839-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|paolo.carlini at oracle dot com    |unassigned at gcc dot gnu.org
             Status|ASSIGNED                    |NEW

--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Paolo has not been around for the last 3 years so unassigning this bug report
from him so someone else can take it if they want. The patch against libcpp is
simple but the testsuite needs to updated or improved.
It also might make sense to have this as an option instead; though
-Wfatal-errors might be enough for that ... (maybe just an improved
documentation for #error in the cpp manual is needed for this change in the
end).

  parent reply	other threads:[~2023-02-23 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 15:49 [Bug c++/48839] New: " john.salmon at deshaw dot com
2011-09-25 11:12 ` [Bug preprocessor/48839] " paolo.carlini at oracle dot com
2014-12-22 16:33 ` egall at gwmail dot gwu.edu
2014-12-22 17:35 ` jason at gcc dot gnu.org
2014-12-22 18:52 ` paolo.carlini at oracle dot com
2022-09-23 13:18 ` redi at gcc dot gnu.org
2023-02-23 20:38 ` pinskia at gcc dot gnu.org [this message]
2023-02-23 20:45 ` pinskia 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-48839-4-pGNmii8e2j@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).