public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65554] ICE: verify_gimple failed Date: Tue, 31 Mar 2015 14:48:00 -0000 [thread overview] Message-ID: <bug-65554-4-vvgWhnRq4k@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65554-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65554 --- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> --- (In reply to Marek Polacek from comment #6) > --- a/gcc/cp/call.c > +++ b/gcc/cp/call.c > @@ -6366,7 +6366,8 @@ convert_like_real (conversion *convs, tree expr, tree > fn, int argnum, > field = next_initializable_field (TYPE_FIELDS (totype)); > CONSTRUCTOR_APPEND_ELT (vec, field, array); > field = next_initializable_field (DECL_CHAIN (field)); > - CONSTRUCTOR_APPEND_ELT (vec, field, size_int (len)); > + CONSTRUCTOR_APPEND_ELT (vec, field, > + build_int_cst (TREE_TYPE (field), len)); > new_ctor = build_constructor (totype, vec); > return get_target_expr_sfinae (new_ctor, complain); > } Not really, it doesn't fix the unreduced testcase. >From gcc-bugs-return-482392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 31 14:20:33 2015 Return-Path: <gcc-bugs-return-482392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 70642 invoked by alias); 31 Mar 2015 14:20: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 70576 invoked by uid 48); 31 Mar 2015 14:20:29 -0000 From: "ossman at cendio dot se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/42159] unwinding issues on darwin Date: Tue, 31 Mar 2015 15:00: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: 4.4.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ossman at cendio dot se X-Bugzilla-Status: RESOLVED 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: cc Message-ID: <bug-42159-4-9xJPlxG1L2@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-42159-4@http.gcc.gnu.org/bugzilla/> References: <bug-42159-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-03/txt/msg03536.txt.bz2 Content-length: 1477 https://gcc.gnu.org/bugzilla/show_bug.cgi?idB159 Pierre Ossman <ossman at cendio dot se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ossman at cendio dot se --- Comment #28 from Pierre Ossman <ossman at cendio dot se> --- I'd like to reopen this issue as we are still seeing this with as new gcc as 4.8.4 (we've been unable to build anything newer). Unfortunately I do not seem to have the access rights to reopen the bug. Help? We've primarily been using 4.6.4 but we also did a test build with 4.8.4 to see if a newer gcc solved the issue. Unfortunately the problem is the same, with the same stack trace. We have however found that the problem seems to be an incompatibility between OS X's unwinder and gcc's (something we found various other gcc bugs and mailing lists discussions on). Or normal way of doing things is to statically link libstdc++ and libgcc_eh. This results in crashing programs. If we inject libSystem before libgcc_eh however, we get the system unwind routines and the program works fine. This is not quite the same as the previous cases mentioned on this bug, but the dumps show that a custom libgcc_s is being used so it should be equivalent. Not sure what the proper fix is but our plan is to bastardise gcc a bit and remove the unwinding routines to make sure the system ones are always used.
next prev parent reply other threads:[~2015-03-31 14:19 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 16:18 [Bug middle-end/65554] New: [5 Regression] " doko at gcc dot gnu.org 2015-03-25 17:55 ` [Bug middle-end/65554] " trippels at gcc dot gnu.org 2015-03-25 18:58 ` jakub at gcc dot gnu.org 2015-03-25 19:03 ` trippels at gcc dot gnu.org 2015-03-25 19:28 ` doko at gcc dot gnu.org 2015-03-26 11:35 ` [Bug c++/65554] " rguenth at gcc dot gnu.org 2015-03-31 14:27 ` mpolacek at gcc dot gnu.org 2015-03-31 14:34 ` mpolacek at gcc dot gnu.org 2015-03-31 14:48 ` mpolacek at gcc dot gnu.org [this message] 2015-03-31 15:19 ` mpolacek at gcc dot gnu.org 2015-04-01 13:08 ` mpolacek at gcc dot gnu.org 2015-04-01 13:11 ` mpolacek at gcc dot gnu.org 2015-04-01 13:35 ` jakub at gcc dot gnu.org 2015-04-01 15:01 ` jakub at gcc dot gnu.org 2015-04-08 9:17 ` mpolacek at gcc dot gnu.org 2015-04-09 15:48 ` [Bug middle-end/65554] [5 Regression] " mpolacek at gcc dot gnu.org 2015-04-09 18:31 ` mpolacek at gcc dot gnu.org 2015-04-09 18:31 ` mpolacek at gcc dot gnu.org 2015-04-10 23:28 ` redi 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-65554-4-vvgWhnRq4k@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).