public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/102718] gtype-desc.c function redefinition error for gt_ggc_xxx (int_hash<unsigned int, 0, 4294967295>&) Date: Wed, 13 Oct 2021 07:34:59 +0000 [thread overview] Message-ID: <bug-102718-4-6kWrwoAcWv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102718-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102718 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords| |build Last reconfirmed| |2021-10-13 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Make gengtype wrap the output in #ifndef GENGTYPE_DEFINED_<type> #define GENGTYPE_DEFINED_<type> ... #endif so any duplicate gets weed out by the preprocessor ;) gengtype is just a not very up to the task of GCC being written in C++ now ...
next prev parent reply other threads:[~2021-10-13 7:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-12 20:44 [Bug other/102718] New: " msebor at gcc dot gnu.org 2021-10-13 7:34 ` rguenth at gcc dot gnu.org [this message] 2021-11-24 21:35 ` [Bug other/102718] " tschwinge 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-102718-4-6kWrwoAcWv@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).