public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64600] [5.0 regression] arm-rtems ICE on valid code (-mcpu=xscale)
Date: Thu, 15 Jan 2015 14:15:00 -0000 [thread overview]
Message-ID: <bug-64600-4-6KM0H0Dg0F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64600-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64600
--- Comment #7 from ktkachov at gcc dot gnu.org ---
(In reply to Ramana Radhakrishnan from comment #5)
> Confirmed - svn+ssh://gcc.gnu.org/svn/gcc/trunk@219641
>
> Passed in a build I had from 13/01/2015.
>
> This is a regression.
now that I reproduced this I can't un-reproduce ;)
This goes for me at least as far back as Dec 15.
The ICE is a gcc_checking_assert so perhaps your 13/01 toolchain doesn't have
checking enabled?
next prev parent reply other threads:[~2015-01-15 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 19:57 [Bug target/64600] New: " joel at gcc dot gnu.org
2015-01-14 19:58 ` [Bug target/64600] " joel at gcc dot gnu.org
2015-01-14 20:11 ` joel at gcc dot gnu.org
2015-01-14 20:12 ` joel at gcc dot gnu.org
2015-01-15 9:18 ` ktkachov at gcc dot gnu.org
2015-01-15 11:48 ` [Bug target/64600] [5.0 regression] " ramana at gcc dot gnu.org
2015-01-15 13:39 ` ktkachov at gcc dot gnu.org
2015-01-15 14:15 ` ktkachov at gcc dot gnu.org [this message]
2015-01-15 14:45 ` ktkachov at gcc dot gnu.org
2015-01-15 15:17 ` joel at gcc dot gnu.org
2015-01-15 19:45 ` rsandifo at gcc dot gnu.org
2015-01-16 13:17 ` ramana at gcc dot gnu.org
2015-01-20 11:04 ` [Bug target/64600] [5 " ktkachov at gcc dot gnu.org
2015-03-13 10:49 ` ktkachov at gcc dot gnu.org
2015-03-13 10:50 ` ktkachov at gcc dot gnu.org
2015-03-18 12:51 ` rguenth 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-64600-4-6KM0H0Dg0F@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: link
Be 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).