public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: emit __float128 typeinfo
Date: Wed, 04 Jun 2014 19:45:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.10.1406042052410.2293@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <538F4FCD.1090500@redhat.com>

On Wed, 4 Jun 2014, Jason Merrill wrote:

> How about, in emit_support_tinfos, using type_for_mode to check for a TF-mode 
> floating point type different from long_double_type_node?

What should I pass as the mode argument? I can't just write TFmode, that 
will fail to compile on platforms that don't define it, and powerpc seems 
likely to call it JFmode instead quite soon. MAX_MODE_FLOAT maybe? But 
then if we configure with long double = __float128, we will miss 
__float80.

Ah, we walk from GET_CLASS_NARROWEST_MODE (MODE_FLOAT) with 
GET_MODE_WIDER_MODE steps and test if the associated type is not in the 
list 0/float/double/long double. I think it should be ok with arm (it 
would be good if they removed their unused XFmode, but I don't even think 
it is necessary).

Is that what you were suggesting? I'll try to write a patch, thanks.

-- 
Marc Glisse

  reply	other threads:[~2014-06-04 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  9:12 Marc Glisse
2014-04-25 11:25 ` Marc Glisse
2014-05-08 14:36   ` Marc Glisse
2014-05-21 17:49 ` Jason Merrill
2014-05-23 10:01   ` Marc Glisse
2014-06-04 16:56     ` Jason Merrill
2014-06-04 19:45       ` Marc Glisse [this message]
2014-06-04 22:00         ` Jason Merrill

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=alpine.DEB.2.10.1406042052410.2293@laptop-mg.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    /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).