public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "miyuki at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/67349] ICE on optimization Date: Tue, 25 Aug 2015 07:28:00 -0000 [thread overview] Message-ID: <bug-67349-4-rQxG13hyXZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67349-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67349 Mikhail Maltsev <miyuki at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |miyuki at gcc dot gnu.org --- Comment #1 from Mikhail Maltsev <miyuki at gcc dot gnu.org> --- I cannot reproduce this with current trunk (h8300 cross), but earlier revisions (including 5.2 release) do crash even on x86_64. I suppose this is the same bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67055#c9 Please provide the output of "h8300-unknown-linux-gcc -v".
next prev parent reply other threads:[~2015-08-25 7:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-25 6:27 [Bug target/67349] New: " ysato at users dot sourceforge.jp 2015-08-25 7:28 ` miyuki at gcc dot gnu.org [this message] 2015-08-25 7:37 ` [Bug tree-optimization/67349] [5 regression] " trippels at gcc dot gnu.org 2015-08-25 7:41 ` trippels 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-67349-4-rQxG13hyXZ@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).