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++/110565] [11/12/13/14 Regression] Incomplete note on why initializing int& with int is ill-formed Date: Mon, 11 Mar 2024 14:27:27 +0000 [thread overview] Message-ID: <bug-110565-4-3eUOpBEwQv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110565-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110565 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- The diagnostic was changed by r5-601-gd02f620dc0bb3b Author: Jason Merrill Date: Wed May 14 17:48:07 2014 re PR c++/20332 (poor diagnostic when bind non lvalue to a reference for default arguments) PR c++/20332 PR c++/21631 * call.c (reference_binding): Treat lvalue/rvalue mismatch and dropped cv-quals as a bad conversion. (convert_like_real) [ck_ref_bind]: Explain them. (compare_ics): Check badness before stripping reference bindings. Handle comparing bad reference bindings. * typeck.c (comp_cv_qualification): Add overload that just takes integers. * cp-tree.h: Declare it.
next prev parent reply other threads:[~2024-03-11 14:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-05 19:36 [Bug c++/110565] New: " blubban at gmail dot com 2023-07-05 23:13 ` [Bug c++/110565] [10/11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-06 8:18 ` rguenth at gcc dot gnu.org 2023-07-07 10:45 ` [Bug c++/110565] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-03-07 23:30 ` law at gcc dot gnu.org 2024-03-11 14:27 ` redi at gcc dot gnu.org [this message] 2024-07-19 13:20 ` [Bug c++/110565] [12/13/14/15 " rguenth 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-110565-4-3eUOpBEwQv@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).