public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/59743] New: [4.9 Regression] ICE: Segmentation fault Date: Thu, 09 Jan 2014 20:41:00 -0000 [thread overview] Message-ID: <bug-59743-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59743 Bug ID: 59743 Summary: [4.9 Regression] ICE: Segmentation fault Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org reduced test case: typedef union { long all; struct { int low; int high; } s; } udwords; int a, b, c, d; void __udivmoddi4() { udwords r; d = __builtin_clz(0); r.s.low = 0; for (; d; --d) { r.s.high = r.s.high << 1 | r.s.low >> a; r.s.low = r.s.low << b >> 1; int s = -r.all; c = s; r.all--; } } % g++ -O2 -c test.ii test.ii: In function ‘void __udivmoddi4()’: test.ii:20:1: internal compiler error: Segmentation fault } ^ 0xb4f8df crash_signal ../../gcc/gcc/toplev.c:337 0xb056c9 reg_used_between_p(rtx_def const*, rtx_def const*, rtx_def const*) ../../gcc/gcc/rtlanal.c:753 0x103e6eb combine_reaching_defs ../../gcc/gcc/ree.c:734 0x103e6eb find_and_remove_re ../../gcc/gcc/ree.c:973 0x103e6eb rest_of_handle_ree ../../gcc/gcc/ree.c:1035 0x103e6eb execute ../../gcc/gcc/ree.c:1074 Please submit a full bug report, >From gcc-bugs-return-439839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 09 20:55:42 2014 Return-Path: <gcc-bugs-return-439839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6133 invoked by alias); 9 Jan 2014 20:41:06 -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 10218 invoked by uid 48); 9 Jan 2014 20:17:06 -0000 From: "rafael.espindola at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO Date: Thu, 09 Jan 2014 20:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: rafael.espindola at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59469-4-icBBqLg1CF@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59469-4@http.gcc.gnu.org/bugzilla/> References: <bug-59469-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: 2014-01/txt/msg00981.txt.bz2 Content-length: 596 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY469 --- Comment #26 from Rafael Avila de Espindola <rafael.espindola at gmail dot com> --- > Yes, is see the weak symbol both in BasicBlock.o and Function.o. > However it gets optimized away when I link them with "-flto -O3" into > libLLVMCore.so (see comment 0). That optimization seems invalid. There is a explicit template instantiation definition, so it is valid for other dsos to have an undefined reference. > Honza says it is an error to have the symbol undefined in > libLLVMAsmParser.so. > (The undefined symbol comes from LLParser.cpp)
next reply other threads:[~2014-01-09 20:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-09 20:41 trippels at gcc dot gnu.org [this message] 2014-01-09 21:05 ` [Bug middle-end/59743] " trippels at gcc dot gnu.org 2014-01-09 21:15 ` jakub at gcc dot gnu.org 2014-01-09 21:20 ` law at redhat dot com 2014-01-09 21:50 ` law at redhat dot com 2014-01-09 21:57 ` law at redhat dot com 2014-01-09 22:00 ` trippels at gcc dot gnu.org 2014-01-09 23:45 ` jakub at gcc dot gnu.org 2014-01-10 5:21 ` law at redhat dot com 2014-01-10 5:34 ` law at redhat dot com 2014-01-10 21:48 ` law at redhat dot com 2014-01-10 22:13 ` law at gcc dot gnu.org 2014-01-10 22:14 ` law at redhat 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-59743-4@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).