public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "h dot b dot furuseth at usit dot uio dot no" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/36887] Please report #pragma GCC poison" location Date: Mon, 21 Jul 2008 11:36:00 -0000 [thread overview] Message-ID: <20080721113606.20408.qmail@sourceware.org> (raw) In-Reply-To: <bug-36887-1038@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from h dot b dot furuseth at usit dot uio dot no 2008-07-21 11:36 ------- Subject: Re: New: Please report #pragma GCC poison" location Sorry about the empty report. Anyway: The warning a.c:2:5: attempt to use poisoned "foo" is not intelligle if one does not know about #pragma GCC poison. (When the poisoning was done by a header file written by someone else.) Please add an additional message foo.h:10: note: "foo" was poisoned here -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36887
next prev parent reply other threads:[~2008-07-21 11:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-07-21 11:29 [Bug preprocessor/36887] New: " h dot b dot furuseth at usit dot uio dot no 2008-07-21 11:36 ` h dot b dot furuseth at usit dot uio dot no [this message] 2008-07-21 14:37 ` [Bug preprocessor/36887] " tromey at gcc dot gnu dot org [not found] <bug-36887-4@http.gcc.gnu.org/bugzilla/> 2021-08-29 21:47 ` pinskia at gcc dot gnu.org 2023-10-02 20:05 ` lhyatt at gcc dot gnu.org 2023-10-23 23:17 ` cvs-commit at gcc dot gnu.org 2023-10-23 23:18 ` 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=20080721113606.20408.qmail@sourceware.org \ --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).