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/62014] [AArch64] Using -mgeneral-regs-only may lead to ICE
Date: Tue, 05 Aug 2014 08:50:00 -0000	[thread overview]
Message-ID: <bug-62014-4-c10eQeWTz2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62014-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from ktkachov at gcc dot gnu.org ---
One crude way to look is by looking for the "w" constraint that signifies usage
of FP registers in the md files and seeing whether those usages are properly
guarded by the 'simd' attribute or by TARGET_FLOAT/TARGET_SIMD.

One quick search shows the absdi2 define_insn_and_split that uses 'w' in its
second alternative to emit "abs\\t%d0, %d1" but doesn't guard it by the 'simd'
attribute. Maybe that's a place to start to construct a testcase


  parent reply	other threads:[~2014-08-05  8:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 21:04 [Bug target/62014] New: " e.menezes at samsung dot com
2014-08-04 21:07 ` [Bug target/62014] " pinskia at gcc dot gnu.org
2014-08-04 21:15 ` e.menezes at samsung dot com
2014-08-04 21:16 ` e.menezes at samsung dot com
2014-08-05  6:55 ` ktkachov at gcc dot gnu.org
2014-08-05  8:33 ` ramana at gcc dot gnu.org
2014-08-05  8:50 ` ktkachov at gcc dot gnu.org [this message]
2014-08-05  9:02 ` ramana at gcc dot gnu.org
2014-08-05  9:04 ` ktkachov at gcc dot gnu.org
2014-08-05 15:36 ` e.menezes at samsung dot com
2014-08-05 15:38 ` ktkachov at gcc dot gnu.org
2014-08-05 15:40 ` e.menezes at samsung dot com
2014-08-05 16:55 ` rearnsha at gcc dot gnu.org
2014-08-05 23:48 ` e.menezes at samsung dot com
2014-08-06  0:02 ` e.menezes at samsung dot com
2014-08-06  8:28 ` ktkachov at gcc dot gnu.org
2014-08-06 22:13 ` e.menezes at samsung dot com

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-62014-4-c10eQeWTz2@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).