public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87163] ICE in extract_insn, at recog.c:2305
Date: Fri, 27 Mar 2020 23:03:01 +0000	[thread overview]
Message-ID: <bug-87163-4-hX7f3SwSos@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87163-4@http.gcc.gnu.org/bugzilla/>

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

Bill Seurer <seurer at linux dot vnet.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |meissner at gcc dot gnu.org,
                   |                            |seurer at linux dot vnet.ibm.com

--- Comment #8 from Bill Seurer <seurer at linux dot vnet.ibm.com> ---
I have duplicated the bug on a cross compile but not natively.

It occurs in the one function:

int do_signbit_if (__ibm128 a) { return __builtin_signbit (a); }

Natively this looks like this when dumped:

;;
;; Full RTL generated for this function:
;;
(note 1 0 4 NOTE_INSN_DELETED)
(note 4 1 2 2 [bb 2] NOTE_INSN_BASIC_BLOCK)
(insn 2 4 3 2 (set (mem/c:TF (reg/f:DI 112 virtual-stack-vars) [1 a+0 S16
A128])
        (reg:TF 33 1 [ a ])) "./signbit-1.c":7:32 -1
     (nil))
...

Cross:
;;
;; Full RTL generated for this function:
;;
(note 1 0 4 NOTE_INSN_DELETED)
(note 4 1 2 2 [bb 2] NOTE_INSN_BASIC_BLOCK)
(insn 2 4 3 2 (set (mem/c:IF (reg/f:DI 112 virtual-stack-vars) [1 a+0 S16
A128])
        (reg:IF 33 1 [ a ])) "./signbit-1.c":7:32 -1
     (nil))
...

Note the reg/mem differences.  There are similar ones further on.

       reply	other threads:[~2020-03-27 23:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-87163-4@http.gcc.gnu.org/bugzilla/>
2020-03-27 23:03 ` seurer at linux dot vnet.ibm.com [this message]
2020-03-28 20:12 ` segher at gcc dot gnu.org
2020-03-28 22:28 ` bergner at gcc dot gnu.org
2020-03-28 23:09 ` bergner at gcc dot gnu.org
2020-03-29 17:15 ` seurer at linux dot vnet.ibm.com
2020-03-29 20:12 ` segher at gcc dot gnu.org
2020-04-01 15:00 ` seurer at linux dot vnet.ibm.com
2020-04-09 17:17 ` seurer at linux dot vnet.ibm.com
2020-04-14 11:38 ` marxin at gcc dot gnu.org
2020-04-14 13:35 ` seurer at linux dot vnet.ibm.com
2020-04-14 13:38 ` marxin 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-87163-4-hX7f3SwSos@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).