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/52566] #include with #pragma once and files' contents is the same Date: Wed, 14 Dec 2022 13:19:54 +0000 [thread overview] Message-ID: <bug-52566-4-FAuq4zkdgk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52566-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52566 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |terra at gnome dot org --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 108101 has been marked as a duplicate of this bug. ***
next prev parent reply other threads:[~2022-12-14 13:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-12 16:25 [Bug preprocessor/52566] New: #include in c++ namespace scope doesn't work properly shihjr at gmail dot com 2012-03-12 16:31 ` [Bug preprocessor/52566] " redi at gcc dot gnu.org 2012-03-12 17:10 ` jakub at gcc dot gnu.org 2012-03-14 10:48 ` redi at gcc dot gnu.org 2022-12-14 13:19 ` pinskia at gcc dot gnu.org [this message] 2022-12-14 13:27 ` [Bug preprocessor/52566] #include with #pragma once and files' contents is the same terra at gnome dot 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-52566-4-FAuq4zkdgk@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).