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 tree-optimization/57980] [4.7/4.8/4.9 Regression] gcc 4.8.1 -foptimize-sibling-calls -O1 ICE in build_int_cst_wide, at tree.c:1210 Date: Fri, 09 Aug 2013 09:42:00 -0000 [thread overview] Message-ID: <bug-57980-4-t45GXlAt2y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57980-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57980 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Known to work| |4.6.3 Component|c |tree-optimization CC| |mpolacek at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org Summary|gcc 4.8.1 |[4.7/4.8/4.9 Regression] |-foptimize-sibling-calls |gcc 4.8.1 |-O1 ICE in |-foptimize-sibling-calls |build_int_cst_wide, at |-O1 ICE in |tree.c:1210 |build_int_cst_wide, at | |tree.c:1210 Target Milestone|--- |4.8.2 Known to fail| |4.7.3, 4.8.1, 4.9.0 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- On it.
next prev parent reply other threads:[~2013-08-09 9:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-25 8:31 [Bug c/57980] New: " zeccav at gmail dot com 2013-07-25 9:08 ` [Bug c/57980] " glisse at gcc dot gnu.org 2013-08-09 9:42 ` mpolacek at gcc dot gnu.org [this message] 2013-08-12 8:47 ` [Bug tree-optimization/57980] [4.7/4.8/4.9 Regression] " mpolacek at gcc dot gnu.org 2013-08-12 8:55 ` mpolacek at gcc dot gnu.org 2013-08-13 13:34 ` mpolacek at gcc dot gnu.org 2013-08-13 13:43 ` mpolacek at gcc dot gnu.org 2013-08-13 13:43 ` 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-57980-4-t45GXlAt2y@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).