public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/48396] std::type_info is implicitly declared Date: Fri, 05 Mar 2021 10:09:55 +0000 [thread overview] Message-ID: <bug-48396-4-xuJw3mEJpz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48396-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48396 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=56468 Summary|Undeclared library types |std::type_info is |accepted in namespace std |implicitly declared Last reconfirmed|2012-04-12 00:00:00 |2021-3-5 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Adjusting the summary because this is specific to std::type_info, it doesn't happen for other types. I think there's some historical reason that G++ pre-defines std::type_info, but maybe we could make that only valid in system headers. It still causes bugs even then, because libstdc++ can accidentally rely on the G++ behaviour, which doesn't work with other compilers (e.g PR 56468).
next prev parent reply other threads:[~2021-03-05 10:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-31 23:33 [Bug c++/48396] New: Undeclared library types accepted in namespace std paolo.carlini at oracle dot com 2012-04-12 12:25 ` [Bug c++/48396] " redi at gcc dot gnu.org 2021-03-05 10:09 ` redi at gcc dot gnu.org [this message] 2021-09-14 20:00 ` [Bug c++/48396] std::type_info is implicitly declared redi at gcc dot gnu.org 2021-09-14 20:05 ` redi at gcc dot gnu.org 2021-09-14 20:49 ` jason at gcc dot gnu.org 2021-09-15 4:27 ` cvs-commit at gcc dot gnu.org 2021-09-15 4:28 ` jason 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-48396-4-xuJw3mEJpz@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).