public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: guojiufu <guojiufu@linux.ibm.com>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: Jiufu Guo via Gcc-patches <gcc-patches@gcc.gnu.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	"Kewen.Lin" <linkw@linux.ibm.com>,
	dje.gcc@gmail.com, linkw@gcc.gnu.org, meissner@linux.ibm.com
Subject: Re: [PATCH] testsuite: update requires for powerpc/float128-cmp2-runnable.c
Date: Thu, 13 Apr 2023 13:35:04 +0800	[thread overview]
Message-ID: <0dbc093a4912f079db61160a3637352f@linux.ibm.com> (raw)
In-Reply-To: <ZDbEW8s8uAUrK+nT@toto.the-meissners.org>

Hi Mike,

On 2023-04-12 22:46, Michael Meissner wrote:
> On Wed, Apr 12, 2023 at 01:31:46PM +0800, Jiufu Guo wrote:
>> I understand that QP insns (e.g. xscmpexpqp) is valid if the system
>> meets ISA3.0, no matter BE/LE, 32-bit/64-bit.
>> I think option -mfloat128-hardware is designed for QP insns.
>> 
>> While there is one issue, on BE machine, when compiling with options
>> "-mfloat128-hardware -m32", an error message is generated:
>> "error: '%<-mfloat128-hardware%>' requires '-m64'"
>> 
>> (I'm wondering if we need to relax this limitation.)
> 
> In the past, the machine independent portion of the compiler demanded 
> that for
> scalar mode, there be an integer mode of the same size, since sometimes 
> moves
> are converted to using an int RTL mode.  Since we don't have TImode 
> support in
> 32-bit, you would get various errors because something tried to do a 
> TImode
> move for KFmode types, and the TImode wasn't available.
> 
> If somebody wants to verify that this now works on 32-bit and/or 
> implements
> TImode on 32-bit, then we can relax the restriction.

Thanks a lot for pointing out this!

BR,
Jeff (Jiufu)

  reply	other threads:[~2023-04-13  5:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  2:09 Jiufu Guo
2023-04-10  9:26 ` Kewen.Lin
2023-04-11  9:14   ` guojiufu
2023-04-11  9:40     ` Kewen.Lin
2023-04-11 15:13       ` Segher Boessenkool
2023-04-12  5:06         ` Jiufu Guo
2023-04-12  5:31           ` Jiufu Guo
2023-04-12 14:46             ` Michael Meissner
2023-04-13  5:35               ` guojiufu [this message]
2023-04-12 12:47         ` Kewen.Lin
2023-04-13  7:42           ` Kewen.Lin
2023-04-13  7:45           ` guojiufu
2023-04-13  8:09             ` Kewen.Lin

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=0dbc093a4912f079db61160a3637352f@linux.ibm.com \
    --to=guojiufu@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@gcc.gnu.org \
    --cc=linkw@linux.ibm.com \
    --cc=meissner@linux.ibm.com \
    --cc=segher@kernel.crashing.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).