public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "terry.guo at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65710] [4.9/5 Regression] Thumb1 ICE caused by no register to spill
Date: Tue, 14 Apr 2015 03:15:00 -0000	[thread overview]
Message-ID: <bug-65710-4-CFhX3SCyfG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65710-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65710

--- Comment #33 from Terry Guo <terry.guo at arm dot com> ---
(In reply to clyon from comment #32)
> > 2015-04-13  Terry Guo  <terry.guo@arm.com>
> > 
> >         PR target/65710
> >         * gcc.target/arm/pr65710.c: New.
> > 
> 
> Terry, any particular reason you use -march=armv6-m instead of -march=armv6 ?
> 
> Some of my test configurations add -marm to RUNTESTFLAGS, and they fail
> because:
> error: target CPU does not support ARM mode
> 
> Can we switch to armv6, or do we need a few additional guards to avoid
> running this test in unsupported configurations?

Thanks for reminding. I just made a stupid copy-paste error here. The correct
options should be "-mthumb -O2 -mfloat-abi=soft" as shown in comment#1. I
reused some test case template and forgot to update the options. I will fix
this soon.


      parent reply	other threads:[~2015-04-14  3:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  7:03 [Bug target/65710] New: [5 " terry.guo at arm dot com
2015-04-09  7:59 ` [Bug target/65710] " rguenth at gcc dot gnu.org
2015-04-09  9:18 ` rguenth at gcc dot gnu.org
2015-04-09  9:30 ` terry.guo at arm dot com
2015-04-09 19:40 ` vmakarov at gcc dot gnu.org
2015-04-09 19:42 ` vmakarov at gcc dot gnu.org
2015-04-10  5:59 ` terry.guo at arm dot com
2015-04-10  6:29 ` jakub at gcc dot gnu.org
2015-04-10 11:30 ` evstupac at gmail dot com
2015-04-10 11:48 ` [Bug target/65710] [4.9 " jakub at gcc dot gnu.org
2015-04-10 13:05 ` yroux at gcc dot gnu.org
2015-04-10 13:06 ` [Bug target/65710] [4.9/5 " jakub at gcc dot gnu.org
2015-04-10 15:25 ` evstupac at gmail dot com
2015-04-10 16:10 ` jakub at gcc dot gnu.org
2015-04-10 16:19 ` vmakarov at gcc dot gnu.org
2015-04-10 16:35 ` jakub at gcc dot gnu.org
2015-04-10 16:38 ` evstupac at gmail dot com
2015-04-10 16:41 ` jakub at gcc dot gnu.org
2015-04-10 16:42 ` vmakarov at gcc dot gnu.org
2015-04-10 16:45 ` jakub at gcc dot gnu.org
2015-04-10 16:47 ` evstupac at gmail dot com
2015-04-10 17:08 ` jakub at gcc dot gnu.org
2015-04-10 18:23 ` yroux at gcc dot gnu.org
2015-04-10 18:53 ` jakub at gcc dot gnu.org
2015-04-10 19:39 ` vmakarov at gcc dot gnu.org
2015-04-10 19:44 ` vmakarov at gcc dot gnu.org
2015-04-10 19:46 ` vmakarov at gcc dot gnu.org
2015-04-10 20:44 ` yroux at gcc dot gnu.org
2015-04-11  7:32 ` jakub at gcc dot gnu.org
2015-04-13  5:22 ` xguo at gcc dot gnu.org
2015-04-13 12:15 ` clyon at gcc dot gnu.org
2015-04-14  3:15 ` terry.guo at arm dot com [this message]

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-65710-4-CFhX3SCyfG@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).