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 middle-end/101204] [12 Regression] infinite recursion in gtype-desc.c since r12-1801-g7036e9ef462fde8181bece4ac4e03f3aa27204dc Date: Sun, 19 Sep 2021 23:13:04 +0000 [thread overview] Message-ID: <bug-101204-4-GAPcCbzrLc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101204-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101204 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- typedef int_hash <location_t, 0, UINT_MAX> xint_hash_t; typedef hash_map<xint_hash_t, nowarn_spec_t> xint_hash_map_t; /* A mapping from a 'location_t' to the warning spec set for it. */ extern GTY(()) xint_hash_map_t *nowarn_map; int_hash has no fields ....
next prev parent reply other threads:[~2021-09-19 23:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-25 7:39 [Bug c/101204] New: infinite recursion in gtype-desc.c dcb314 at hotmail dot com 2021-06-25 8:39 ` [Bug middle-end/101204] " jakub at gcc dot gnu.org 2021-06-25 23:49 ` msebor at gcc dot gnu.org 2021-06-26 7:48 ` dcb314 at hotmail dot com 2021-07-01 9:24 ` [Bug middle-end/101204] [12 Regression] infinite recursion in gtype-desc.c since r12-1801-g7036e9ef462fde8181bece4ac4e03f3aa27204dc marxin at gcc dot gnu.org 2021-09-19 23:01 ` pinskia at gcc dot gnu.org 2021-09-19 23:05 ` pinskia at gcc dot gnu.org 2021-09-19 23:13 ` pinskia at gcc dot gnu.org [this message] 2021-11-08 9:58 ` tschwinge at gcc dot gnu.org 2021-11-09 12:21 ` cvs-commit at gcc dot gnu.org 2021-11-09 12:29 ` 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-101204-4-GAPcCbzrLc@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).