public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug c++/98967] New: warning to spot recursive include graph
@ 2021-02-04 14:01 nathan at gcc dot gnu.org
2021-02-04 14:40 ` [Bug c++/98967] " redi at gcc dot gnu.org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: nathan at gcc dot gnu.org @ 2021-02-04 14:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967
Bug ID: 98967
Summary: warning to spot recursive include graph
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nathan at gcc dot gnu.org
Target Milestone: ---
recursive headers can slip in unnoticed (eg the new<...>exception loop found in
2020). Often these are harmless, but with c++20 header-units they can be
fatal. They are hard to locate, as absent modules they could be harmless.
Add a warning to spot them in the preprocessor.
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug c++/98967] warning to spot recursive include graph 2021-02-04 14:01 [Bug c++/98967] New: warning to spot recursive include graph nathan at gcc dot gnu.org @ 2021-02-04 14:40 ` redi at gcc dot gnu.org 2021-02-05 9:45 ` egallager at gcc dot gnu.org ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: redi at gcc dot gnu.org @ 2021-02-04 14:40 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-02-04 Severity|normal |enhancement Status|UNCONFIRMED |NEW Keywords| |diagnostic Ever confirmed|0 |1 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/98967] warning to spot recursive include graph 2021-02-04 14:01 [Bug c++/98967] New: warning to spot recursive include graph nathan at gcc dot gnu.org 2021-02-04 14:40 ` [Bug c++/98967] " redi at gcc dot gnu.org @ 2021-02-05 9:45 ` egallager at gcc dot gnu.org 2021-02-19 14:57 ` nathan at gcc dot gnu.org 2021-05-04 12:32 ` rguenth at gcc dot gnu.org 3 siblings, 0 replies; 5+ messages in thread From: egallager at gcc dot gnu.org @ 2021-02-05 9:45 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=96842 CC| |egallager at gcc dot gnu.org --- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> --- Fixing bug 96842 would also help here (not exactly the same thing, but serves a similar purpose) ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/98967] warning to spot recursive include graph 2021-02-04 14:01 [Bug c++/98967] New: warning to spot recursive include graph nathan at gcc dot gnu.org 2021-02-04 14:40 ` [Bug c++/98967] " redi at gcc dot gnu.org 2021-02-05 9:45 ` egallager at gcc dot gnu.org @ 2021-02-19 14:57 ` nathan at gcc dot gnu.org 2021-05-04 12:32 ` rguenth at gcc dot gnu.org 3 siblings, 0 replies; 5+ messages in thread From: nathan at gcc dot gnu.org @ 2021-02-19 14:57 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967 Nathan Sidwell <nathan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot gnu.org --- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> --- discussing with clang guys, Richard wondered whether we'd make this the default (eventually?). to do that, would require a smarter implementation that explicitly pushed and popped the line table (or an appropriate action with include translate). That'd also make it work for #import and #pragma once. ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/98967] warning to spot recursive include graph 2021-02-04 14:01 [Bug c++/98967] New: warning to spot recursive include graph nathan at gcc dot gnu.org ` (2 preceding siblings ...) 2021-02-19 14:57 ` nathan at gcc dot gnu.org @ 2021-05-04 12:32 ` rguenth at gcc dot gnu.org 3 siblings, 0 replies; 5+ messages in thread From: rguenth at gcc dot gnu.org @ 2021-05-04 12:32 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-05-04 12:32 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-02-04 14:01 [Bug c++/98967] New: warning to spot recursive include graph nathan at gcc dot gnu.org 2021-02-04 14:40 ` [Bug c++/98967] " redi at gcc dot gnu.org 2021-02-05 9:45 ` egallager at gcc dot gnu.org 2021-02-19 14:57 ` nathan at gcc dot gnu.org 2021-05-04 12:32 ` rguenth at gcc dot gnu.org
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).