public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52347] -Wno-tabs -Wall -Wno-tabs still warns about tabs Date: Fri, 14 Jun 2013 21:27:00 -0000 [thread overview] Message-ID: <bug-52347-4-4ODdv2rkFL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52347-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52347 --- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Simon Richter from comment #2) > In 4.8, this causes build failures for me: > > $ g++ -g -Wall -W -Werror -Wno-unused -I. -o stage1/tree_bison_lex.o -c > tree_bison_lex.cpp > tree_bison_lex.cpp:1744:13: error: unused parameter 'yyscanner' > [-Werror=unused-parameter] Could you attach a self-contained preprocessed testcase? See http://gcc.gnu.org/bugs/ >From gcc-bugs-return-424380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 14 21:41:19 2013 Return-Path: <gcc-bugs-return-424380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5479 invoked by alias); 14 Jun 2013 21:41:19 -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 5459 invoked by uid 48); 14 Jun 2013 21:41:15 -0000 From: "gdjss2728 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/57619] New: std::unordered_map and std::unordered_multimap::insert invoking std::pair move constructor Date: Fri, 14 Jun 2013 21:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gdjss2728 at gmail 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-57619-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-06/txt/msg00759.txt.bz2 Content-length: 1217 http://gcc.gnu.org/bugzilla/show_bug.cgi?idW619 Bug ID: 57619 Summary: std::unordered_map and std::unordered_multimap::insert invoking std::pair move constructor Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: gdjss2728 at gmail dot com The following code is invoking the std::pair move constructor: int main () { std::unordered_map<std::string, std::string> mymap; std::unordered_multimap<std::string, std::string> mymultimap; std::pair<std::string, std::string> mypair{std::string("key"), std::string("value")}; mymultimap.insert(mypair); // std::pair move constructor invoked here mymap.insert(mypair); // strings already moved out! } This seems related to http://gcc.gnu.org/bugzilla/show_bug.cgi?idS657. As far as I can tell, overload resolution is choosing `insert(_Pair&& __x)` over `insert(const value_type& __x)`. Since this is an lvalue, the latter should be chosen. This happens for std::unordered_map::insert and std::unordered_multimap::insert.
next prev parent reply other threads:[~2013-06-14 21:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-23 8:37 [Bug fortran/52347] New: " burnus at gcc dot gnu.org 2012-02-23 8:42 ` [Bug fortran/52347] " manu at gcc dot gnu.org 2013-06-14 19:43 ` Simon.Richter at hogyros dot de 2013-06-14 21:27 ` manu at gcc dot gnu.org [this message] 2013-06-14 23:15 ` Simon.Richter at hogyros dot de 2013-06-15 9:36 ` manu at gcc dot gnu.org 2014-12-11 17:41 ` burnus 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-52347-4-4ODdv2rkFL@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).