public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51747] [DR 1467] [C++11] cannot call defaulted copy constructor using list-initialization Date: Sun, 25 Jan 2015 18:35:00 -0000 [thread overview] Message-ID: <bug-51747-4-ORs4lN3ggy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51747-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51747 --- Comment #11 from Ville Voutilainen <ville.voutilainen at gmail dot com> --- Also, struct base { int x; }; struct derived : base { derived(const base &state) : base{state} {} }; is diagnosed with base-aggr-init2.cpp: In constructor ‘derived::derived(const base&)’: base-aggr-init2.cpp:7:17: error: cannot convert ‘const base’ to ‘int’ in initialization : base{state} ^ so it doesn't look like Core 1467 is handled in base class initializers at all. >From gcc-bugs-return-474792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 25 18:37:36 2015 Return-Path: <gcc-bugs-return-474792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 14985 invoked by alias); 25 Jan 2015 18:35:15 -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 30718 invoked by uid 48); 25 Jan 2015 18:08:03 -0000 From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51747] [DR 1467] [C++11] cannot call defaulted copy constructor using list-initialization Date: Sun, 25 Jan 2015 18:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.7.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: ville.voutilainen at gmail dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-51747-4-sTeEKNcD0C@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-51747-4@http.gcc.gnu.org/bugzilla/> References: <bug-51747-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg02787.txt.bz2 Content-length: 537 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51747 --- Comment #10 from Ville Voutilainen <ville.voutilainen at gmail dot com> --- This code fails with the current trunk: struct B {}; struct D : B {D(B b) : B{b} {}}; base-aggr-init.cpp: In constructor ‘D::D(B)’: base-aggr-init.cpp:2:27: error: too many initializers for ‘B’ struct D : B {D(B b) : B{b} {}}; ^ As far as I can see, the function process_init_constructor_record in typeck2.c emits the diagnostic. >From gcc-bugs-return-474795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 25 20:33:12 2015 Return-Path: <gcc-bugs-return-474795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 7204 invoked by alias); 25 Jan 2015 20:32:33 -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 6353 invoked by uid 48); 25 Jan 2015 20:30:32 -0000 From: "mittorn at sibmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/64790] New: gcc generates unreliable code on arm with -mstructure-size-boundary2 Date: Sun, 25 Jan 2015 20:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.8.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mittorn at sibmail 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-64790-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: 2015-01/txt/msg02789.txt.bz2 Content-length: 732 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd790 Bug ID: 64790 Summary: gcc generates unreliable code on arm with -mstructure-size-boundary2 Product: gcc Version: 4.8.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mittorn at sibmail dot com After rebuilding many of system libraries with -mstructure-size-boundary2 i found that fsck.fat does not work propertly and all gtk applications does not correctly handle input and xfce4-desktop shows icons with wrong coordinates After rebuilding dosfstools and libX11 problem was solved
next prev parent reply other threads:[~2015-01-25 18:35 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-03 22:04 [Bug c++/51747] New: [C++11] cannot call " redi at gcc dot gnu.org 2012-02-02 6:08 ` [Bug c++/51747] [C++11] cannot call defaulted " pinskia at gcc dot gnu.org 2013-04-25 11:30 ` redi at gcc dot gnu.org 2014-03-19 17:29 ` [Bug c++/51747] [DR 1467] " redi at gcc dot gnu.org 2014-03-19 17:31 ` redi at gcc dot gnu.org 2014-03-20 21:27 ` jason at gcc dot gnu.org 2014-03-24 16:03 ` jason at gcc dot gnu.org 2014-04-11 18:25 ` jason at gcc dot gnu.org 2014-05-05 16:05 ` jason at gcc dot gnu.org 2015-01-16 9:10 ` ville.voutilainen at gmail dot com 2015-01-16 17:04 ` tom at honermann dot net 2015-01-25 18:35 ` ville.voutilainen at gmail dot com [this message] 2015-04-22 12:01 ` jakub at gcc dot gnu.org 2015-05-07 16:47 ` jason at gcc dot gnu.org 2015-05-07 16:47 ` jason at gcc dot gnu.org 2015-05-07 16:48 ` jason at gcc dot gnu.org 2015-06-09 16:56 ` jason 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-51747-4-ORs4lN3ggy@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).