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++/59244] [c++11] can't specialize template on ref-qualified member function pointer type Date: Sat, 23 Nov 2013 22:19:00 -0000 [thread overview] Message-ID: <bug-59244-4-8fGpPL8Fi4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59244-4@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 2446 bytes --] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59244 --- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- This seems to be fixed in gcc 4.8.2 and in gcc 4.9.0 HEAD >From gcc-bugs-return-435662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 22:30:02 2013 Return-Path: <gcc-bugs-return-435662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 9580 invoked by alias); 23 Nov 2013 22:30:01 -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 9496 invoked by uid 48); 23 Nov 2013 22:29:58 -0000 From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59258] usan: ICE(segfault): stack-buffer-overflow with -fsanitize=undefined Date: Sat, 23 Nov 2013 22:30: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: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59258-4-Y39s68W2HR@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59258-4@http.gcc.gnu.org/bugzilla/> References: <bug-59258-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-11/txt/msg02439.txt.bz2 Content-length: 435 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY258 --- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> --- (In reply to Tobias Burnus from comment #4) > Except for staring at the -fsanitize=null code, I don't have any good idea > how to debug this - valgrind and an -fsanitizeddress instrumented GCC > don't help. Seems like we're passing bogus location. Can you e-mail me the unreduced testcase? I'll look into it.
next prev parent reply other threads:[~2013-11-23 22:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-22 5:41 [Bug c++/59244] New: " eric.niebler at gmail dot com 2013-11-23 22:19 ` daniel.kruegler at googlemail dot com [this message] 2014-11-26 16:20 ` [Bug c++/59244] " paolo.carlini at oracle dot com
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-59244-4-8fGpPL8Fi4@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).