public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tsaunders at mozilla dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/61598] [4.10 regression] fold-const.c:14755:37: error: no matching function for call to 'hash_table<pointer_hash<tree_node> >::find_slot Date: Tue, 24 Jun 2014 19:09:00 -0000 [thread overview] Message-ID: <bug-61598-4-Kj8jbOHoIf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61598-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61598 Trevor Saunders <tsaunders at mozilla dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tsaunders at mozilla dot com --- Comment #2 from Trevor Saunders <tsaunders at mozilla dot com> --- So we went from find_slot taking a const uninon tree_node *& to taking a union tree_node * const& I tend to think that the later is more "correct" since the type of thing in the hash table and hence the thing that is const is a union tree_node *. Further the result of find_slot is a tree_node ** which is not const. So I think the appropriate solution is to just const_cast to tree, but a sanity check of that would be nice.
next prev parent reply other threads:[~2014-06-24 19:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-24 17:28 [Bug bootstrap/61598] New: " dimhen at gmail dot com 2014-06-24 19:09 ` tsaunders at mozilla dot com [this message] 2014-06-25 8:30 ` [Bug bootstrap/61598] " rguenth at gcc dot gnu.org 2014-06-25 16:02 ` tbsaunde at gcc dot gnu.org 2014-06-25 18:42 ` tbsaunde 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-61598-4-Kj8jbOHoIf@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).