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 middle-end/63879] ICE compiling Linux Kernel fs/ext3/namei.c Date: Sat, 15 Nov 2014 07:08:00 -0000 [thread overview] Message-ID: <bug-63879-4-bo2kjrdkFN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63879-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63879 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2014-11-15 Target Milestone|--- |5.0 Ever confirmed|0 |1 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- That would mean we hit infinite recursion. But I can't reproduce this on x86-64 with any optimization level - can you please specify the command-line options?
next prev parent reply other threads:[~2014-11-15 7:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-14 22:51 [Bug c/63879] New: " sasha.levin at oracle dot com 2014-11-15 7:08 ` mpolacek at gcc dot gnu.org [this message] 2014-11-15 16:26 ` [Bug middle-end/63879] " 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-bo2kjrdkFN@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).