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/108108] "gcc -MM" fails to list all dependencies
Date: Wed, 14 Dec 2022 18:05:24 +0000 [thread overview]
Message-ID: <bug-108108-4-xBoW1PP8Qh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108108-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108108
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|other |preprocessor
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>This is a spin-off from bug 52566
I don't think this is different issue from that bug.
The preprocessor decided it was the same file.
This is why '#pragma once' should not be used.
next prev parent reply other threads:[~2022-12-14 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 18:01 [Bug other/108108] New: " terra at gnome dot org
2022-12-14 18:05 ` pinskia at gcc dot gnu.org [this message]
2022-12-14 18:11 ` [Bug preprocessor/108108] " pinskia at gcc dot gnu.org
2022-12-14 18:11 ` pinskia at gcc dot gnu.org
2022-12-14 18:40 ` 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-108108-4-xBoW1PP8Qh@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).