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: Tue, 14 Sep 2021 20:05:09 +0000	[thread overview]
Message-ID: <bug-48396-4-jEsePQZpRZ@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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
cp/rtti.c defines:

/* Declare language defined type_info type and a pointer to const
   type_info.  This is incomplete here, and will be completed when
   the user #includes <typeinfo>.  There are language defined
   restrictions on what can be done until that is included.  Create
   the internal versions of the ABI types.  */

void
init_rtti_processing (void)
{
  push_nested_namespace (std_node);
  tree type_info_type = xref_tag (class_type, get_identifier ("type_info"));
  pop_nested_namespace (std_node);
  const_type_info_type_node
    = cp_build_qualified_type (type_info_type, TYPE_QUAL_CONST);
  type_info_ptr_type = build_pointer_type (const_type_info_type_node);

  vec_alloc (unemitted_tinfo_decls, 124);

  create_tinfo_types ();
}

Is there a way to do that without making it visible to user code? Or without
implicitly adding it to the GMF?

  parent reply	other threads:[~2021-09-14 20:05 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 ` [Bug c++/48396] std::type_info is implicitly declared redi at gcc dot gnu.org
2021-09-14 20:00 ` redi at gcc dot gnu.org
2021-09-14 20:05 ` redi at gcc dot gnu.org [this message]
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-jEsePQZpRZ@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).