public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sasha.levin at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/63879] New: ICE compiling Linux Kernel fs/ext3/namei.c Date: Fri, 14 Nov 2014 22:51:00 -0000 [thread overview] Message-ID: <bug-63879-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63879 Bug ID: 63879 Summary: ICE compiling Linux Kernel fs/ext3/namei.c Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sasha.levin at oracle dot com CC: mpolacek at gcc dot gnu.org Created attachment 33978 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33978&action=edit Preprocessed source I'm seeing very high memory usage followed by: {standard input}: Assembler messages: {standard input}:2183: Warning: end of file not at end of a line; newline inserted {standard input}:4163: Error: number of operands mismatch for `movq' {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive gcc: internal compiler error: Killed (program cc1) 0x40c3cc execute ../../gcc/gcc.c:2912 0x410917 driver::do_spec_on_infiles() const ../../gcc/gcc.c:7674 0x40322b driver::main(int, char**) ../../gcc/gcc.c:6911 I've bisected this issue down to: commit 1043013c91c08e3d8cd665b3f960f658918d69fe Author: mpolacek <mpolacek@138bc75d-0d04-0410-961f-82ee72b054a4> Date: Fri Nov 14 11:57:05 2014 +0000 * fold-const.c (fold_negate_expr): Don't fold INTEGER_CST if that overflows when SANITIZE_SI_OVERFLOW is on. Guard -(-A) folding with TYPE_OVERFLOW_SANITIZED. * c-c++-common/ubsan/overflow-negate-3.c: New test. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@217556 138bc75d-0d04-0410-961f-82ee7 Preprocessed fs/ext3/namei.c attached.
next reply other threads:[~2014-11-14 22:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-14 22:51 sasha.levin at oracle dot com [this message] 2014-11-15 7:08 ` [Bug middle-end/63879] " mpolacek at gcc dot gnu.org 2014-11-15 16:26 ` sasha.levin at oracle dot com 2014-11-15 16:40 ` hjl.tools at gmail dot com 2014-11-15 16:43 ` sasha.levin at oracle dot com 2014-11-15 17:34 ` hjl.tools at gmail dot com 2014-11-15 17:48 ` sasha.levin at oracle dot com 2014-11-16 13:10 ` mpolacek at gcc dot gnu.org 2014-11-17 9:42 ` [Bug middle-end/63879] [5 Regression] ICE compiling Linux Kernel fs/ext3/namei.c with -fsanitize=undefined rguenth at gcc dot gnu.org 2014-11-18 17:11 ` trippels at gcc dot gnu.org 2014-11-19 12:03 ` mpolacek at gcc dot gnu.org 2014-11-19 12:04 ` mpolacek 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-63879-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).