public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58713] error: cannot bind ‘std::ostream {aka std::basic_ostream<char>}’ lvalue to ‘std::basic_ostream<char>&&’ Date: Mon, 14 Oct 2013 06:29:00 -0000 [thread overview] Message-ID: <bug-58713-4-YgqMJ4rqKE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58713-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58713 --- Comment #3 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- (In reply to Jonathan Wakely from comment #1) > I've tried to improve it in the past, but I think there's no easy way to do > it. A possible fix might be to change the Standard ;-) Despite the smiley I seriously consider to make the proposal/open an issue that the "all-eating" signature template <class charT, class traits, class T> basic_ostream<charT, traits>& operator<<(basic_ostream<charT, traits>&& os, const T& x); should be constrained and should not participate in overload resolution unless the expression os << x would be well-formed (similar for the corresponding extractor). My current guess is that this would also improve the diagnostics in this case, is that right? >From gcc-bugs-return-431604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 14 06:29:09 2013 Return-Path: <gcc-bugs-return-431604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 7302 invoked by alias); 14 Oct 2013 06:29:08 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 7149 invoked by uid 48); 14 Oct 2013 06:29:04 -0000 From: "samsonov at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/58718] Invalid check in libsanitizer Date: Mon, 14 Oct 2013 06:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: samsonov at google dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-58718-4-zOM851JFIn@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-58718-4@http.gcc.gnu.org/bugzilla/> References: <bug-58718-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-10/txt/msg00748.txt.bz2 Content-length: 556 http://gcc.gnu.org/bugzilla/show_bug.cgi?idX718 Alexey Samsonov <samsonov at google dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samsonov at google dot com --- Comment #2 from Alexey Samsonov <samsonov at google dot com> --- I've already fixed the problem with crashes caused by small "malloc_context_size" values. I think you should wait till the ASan runtime will be merged from LLVM into GCC.
next prev parent reply other threads:[~2013-10-14 6:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-13 12:20 [Bug c++/58713] New: " ali.baharev at gmail dot com 2013-10-14 0:10 ` [Bug c++/58713] " redi at gcc dot gnu.org 2013-10-14 0:22 ` ali.baharev at gmail dot com 2013-10-14 6:29 ` daniel.kruegler at googlemail dot com [this message] 2013-10-14 7:04 ` glisse at gcc dot gnu.org 2013-10-14 7:09 ` daniel.kruegler at googlemail dot com 2013-10-14 13:17 ` daniel.kruegler at googlemail dot com 2013-10-14 13:26 ` redi 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-58713-4-YgqMJ4rqKE@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).