public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: CDImode in reg
Date: Tue, 04 Oct 2011 09:33:00 -0000	[thread overview]
Message-ID: <CAJ-J9_VRBj7yY4j8-yWnzYjgoOYRLP-rxKLbDS7BwWVyyCvxoA@mail.gmail.com> (raw)

Hi,

I'm trying to get the gcc testsuite passing for my new target port.
The last ICE deals with complex long long (gcc.c-torture/compile/20000804-1.c).
My target has 16-bit wide int, and regs can hold DImode max.

code:

  __complex__ long long v;
  asm("": "+r" (v) : "r" (0), "r" (1));

Is such the testcase an expected fail or not ?
Operations on complex are often split into DI operations. But the
target cannot hold a whole CDI into one register, but could hold 2 DI
into 2 distinct DI regs.

If it is an xfail, is there a way handle such a case at higher level
to prevent an ICE and generate a more user friendly error message ?

If it is a fail, I have no idea how to fix this (pb with
init_move_cost(CDImode), with a gcc_assert
(have_regs_of_mode[CDImode]))

Thanks,
Aurélien

             reply	other threads:[~2011-10-04  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  9:33 Aurelien Buhrig [this message]
2011-10-04 14:07 ` Ian Lance Taylor
2011-10-04 14:53   ` Aurelien Buhrig
2011-10-04 15:52     ` Segher Boessenkool
2011-10-04 16:19     ` Ian Lance Taylor
2011-10-04 17:00       ` Aurelien Buhrig
2011-10-04 18:22         ` Ian Lance Taylor
2011-10-05  7:31           ` Aurelien Buhrig
2011-10-05 13:55             ` Ian Lance Taylor

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=CAJ-J9_VRBj7yY4j8-yWnzYjgoOYRLP-rxKLbDS7BwWVyyCvxoA@mail.gmail.com \
    --to=aurelien.buhrig.gcc@gmail.com \
    --cc=gcc-help@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).