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++/59312] Incorrect warning "defaulted move assignment for ... calls a non-trivial move assignment operator for virtual base ..." Date: Thu, 28 Nov 2013 11:28:00 -0000 [thread overview] Message-ID: <bug-59312-4-gIuGfc2jjw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59312-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59312 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Alexander Khovansky from comment #0) > — any direct or indirect virtual base class. I'm looking at N3290, but was looking for a bullet starting with that text. Now I see it's at the very end of the last bullet, sorry. In any case, that isn't in the current draft, it was removed by http://open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1402 and G++ implements that resolution. >From gcc-bugs-return-436109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Nov 28 11:29:56 2013 Return-Path: <gcc-bugs-return-436109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6409 invoked by alias); 28 Nov 2013 11:29:56 -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 5009 invoked by uid 48); 28 Nov 2013 11:29:20 -0000 From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59327] warning in expand_used_vars Date: Thu, 28 Nov 2013 11:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: amylaar at gcc dot gnu.org 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: Message-ID: <bug-59327-4-7YgH0NS9YY@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59327-4@http.gcc.gnu.org/bugzilla/> References: <bug-59327-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/msg02886.txt.bz2 Content-length: 252 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY327 --- Comment #1 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> --- The warning also happens when using g++ (GCC) 4.9.0 20131128 (experimental), and when building gcc for target epiphany-elf.
next prev parent reply other threads:[~2013-11-28 11:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-27 13:49 [Bug c++/59312] New: " alexander.o.khovansky at yandex dot com 2013-11-27 14:35 ` [Bug c++/59312] " redi at gcc dot gnu.org 2013-11-28 11:28 ` redi at gcc dot gnu.org [this message] 2015-03-25 19:09 ` 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-59312-4-gIuGfc2jjw@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).