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++/63707] Brace initialization of array sometimes fails if no copy constructor Date: Wed, 28 Jan 2015 11:52:00 -0000 [thread overview] Message-ID: <bug-63707-4-3If3TLEYWy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63707-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63707 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- The member array case only fails when the array element has a user-defined destructor Here's the failing testcase repeated from the attachment and reduced slightly: struct Child { Child (int); ~Child (); Child (const Child &) = delete; }; struct Parent { Parent () : children {{5}, {7}} {} Child children[2]; }; i.cc: In constructor ‘Parent::Parent()’: i.cc:12:35: error: use of deleted function ‘Child::Child(const Child&)’ Parent () : children {{5}, {7}} {} ^ i.cc:6:5: note: declared here Child (const Child &) = delete; ^ Commenting out the destructor declaration allows it to compile. >From gcc-bugs-return-475225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 28 11:53:59 2015 Return-Path: <gcc-bugs-return-475225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 26770 invoked by alias); 28 Jan 2015 11:53:59 -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 26538 invoked by uid 48); 28 Jan 2015 11:53:54 -0000 From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64829] [ARM] ICE at -O3 in vect_get_vec_def_for_stmt_copy Date: Wed, 28 Jan 2015 11:53:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ktkachov at gcc dot gnu.org X-Bugzilla-Status: NEW 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-64829-4-mDMFpWyh8Y@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64829-4@http.gcc.gnu.org/bugzilla/> References: <bug-64829-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/msg03219.txt.bz2 Content-length: 332 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd829 --- Comment #4 from ktkachov at gcc dot gnu.org --- > > are you sure it isn't already fixed? Don't think so. It ICEs for me with r220203. I'm using the options -mfpu=neon -mfloat-abi=hard -O3 -march=armv7-a. The -mfloat-abi=hard is important, it doesn't reproduce without it
next prev parent reply other threads:[~2015-01-28 11:52 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-01 18:44 [Bug c++/63707] New: " john.lindgren at aol dot com 2014-11-01 18:44 ` [Bug c++/63707] " john.lindgren at aol dot com 2014-11-01 18:45 ` john.lindgren at aol dot com 2014-11-01 18:49 ` john.lindgren at aol dot com 2014-12-12 15:02 ` ville.voutilainen at gmail dot com 2015-01-28 11:52 ` redi at gcc dot gnu.org [this message] 2015-01-31 20:34 ` redi at gcc dot gnu.org 2015-01-31 20:35 ` redi at gcc dot gnu.org 2020-12-06 19:59 ` eyalroz at technion dot ac.il 2020-12-10 19:17 ` jakub at gcc dot gnu.org 2021-01-12 23:35 ` pdimov at gmail dot com 2021-01-13 1:32 ` mpolacek at gcc dot gnu.org 2021-01-13 1:32 ` mpolacek at gcc dot gnu.org 2021-01-14 20:36 ` jason at gcc dot gnu.org 2021-01-15 18:39 ` cvs-commit at gcc dot gnu.org 2021-01-15 18:57 ` jason at gcc dot gnu.org 2021-01-29 16:00 ` cvs-commit at gcc dot gnu.org 2021-01-29 16:23 ` cvs-commit at gcc dot gnu.org 2021-01-29 18:18 ` jason at gcc dot gnu.org 2021-01-29 19:31 ` eyalroz1 at gmx dot com 2021-08-13 8:32 ` pinskia at gcc dot gnu.org 2021-12-09 7:35 ` pinskia at gcc dot gnu.org 2022-08-31 12:28 ` marxin 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-63707-4-3If3TLEYWy@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).