public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65979] [4.9/5/6 Regression] [SH] Wrong code is generated with stage1 compiler Date: Thu, 21 May 2015 13:37:00 -0000 [thread overview] Message-ID: <bug-65979-4-bRwjzkYOwL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65979-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65979 --- Comment #23 from Kazumoto Kojima <kkojima at gcc dot gnu.org> --- Ouch. The peephole in problem was added at gcc-5 not at 4.9. The above patch should fix the original conftest.c issue, but debien 4.9-16 problem would be an another issue. Sorry for my confusion.
next prev parent reply other threads:[~2015-05-21 13:37 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-02 8:15 [Bug target/65979] New: internal compiler error: in make_edges, at tree-cfg.c:923 glaubitz at physik dot fu-berlin.de 2015-05-02 8:15 ` [Bug target/65979] " glaubitz at physik dot fu-berlin.de 2015-05-02 13:00 ` [Bug target/65979] Multiple issues in conftest.c prevent build on sh4-linux-gnu kkojima at gcc dot gnu.org 2015-05-02 13:14 ` kkojima at gcc dot gnu.org 2015-05-03 15:17 ` glaubitz at physik dot fu-berlin.de 2015-05-09 11:42 ` glaubitz at physik dot fu-berlin.de 2015-05-10 0:19 ` kkojima at gcc dot gnu.org 2015-05-11 22:16 ` glaubitz at physik dot fu-berlin.de 2015-05-11 22:34 ` glaubitz at physik dot fu-berlin.de 2015-05-17 17:11 ` glaubitz at physik dot fu-berlin.de 2015-05-20 2:58 ` kkojima at gcc dot gnu.org 2015-05-20 3:03 ` kkojima at gcc dot gnu.org 2015-05-20 7:04 ` olegendo at gcc dot gnu.org 2015-05-20 7:58 ` olegendo at gcc dot gnu.org 2015-05-20 10:01 ` kkojima at gcc dot gnu.org 2015-05-20 11:15 ` glaubitz at physik dot fu-berlin.de 2015-05-20 20:31 ` olegendo at gcc dot gnu.org 2015-05-21 10:25 ` kkojima at gcc dot gnu.org 2015-05-21 10:47 ` olegendo at gcc dot gnu.org 2015-05-21 12:03 ` [Bug target/65979] [4.9/5/6 Regression] [SH] Wrong code is generated with stage1 compiler kkojima at gcc dot gnu.org 2015-05-21 13:37 ` kkojima at gcc dot gnu.org [this message] 2015-05-21 15:02 ` glaubitz at physik dot fu-berlin.de 2015-05-21 21:08 ` olegendo at gcc dot gnu.org 2015-05-21 22:21 ` kkojima at gcc dot gnu.org 2015-05-25 11:31 ` glaubitz at physik dot fu-berlin.de 2015-05-26 10:01 ` olegendo at gcc dot gnu.org 2015-05-26 22:32 ` kkojima at gcc dot gnu.org 2015-05-26 22:37 ` kkojima at gcc dot gnu.org 2015-05-26 23:11 ` [Bug target/65979] [5/6 " kkojima at gcc dot gnu.org 2015-05-27 11:27 ` glaubitz at physik dot fu-berlin.de 2015-05-27 12:12 ` olegendo at gcc dot gnu.org 2015-06-24 12:37 ` olegendo at gcc dot gnu.org 2015-06-24 13:41 ` olegendo at gcc dot gnu.org 2015-06-24 23:59 ` kkojima at gcc dot gnu.org 2015-06-25 10:10 ` kkojima at gcc dot gnu.org 2015-06-25 12:04 ` glaubitz at physik dot fu-berlin.de 2015-06-25 13:58 ` kkojima at gcc dot gnu.org 2015-06-25 22:30 ` kkojima at gcc dot gnu.org 2015-06-25 23:12 ` olegendo at gcc dot gnu.org 2015-06-25 23:58 ` olegendo at gcc dot gnu.org 2015-06-26 0:18 ` kkojima at gcc dot gnu.org 2015-06-27 0:47 ` olegendo at gcc dot gnu.org 2015-07-26 5:12 ` olegendo at gcc dot gnu.org 2015-07-26 16:36 ` glaubitz at physik dot fu-berlin.de 2015-07-27 3:53 ` olegendo 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-65979-4-bRwjzkYOwL@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).