From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Alexander Monakov <amonakov@ispras.ru>,
gcc@gcc.gnu.org, Vladislav Ivanishin <vlad@ispras.ru>
Subject: Re: LTO remapping/deduction of machine modes of types/decls
Date: Wed, 04 Jan 2017 10:14:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1701041112220.5294@t29.fhfr.qr> (raw)
In-Reply-To: <20170102190255.GG21933@tucnak>
On Mon, 2 Jan 2017, Jakub Jelinek wrote:
> On Mon, Jan 02, 2017 at 09:49:55PM +0300, Alexander Monakov wrote:
> > On Mon, 2 Jan 2017, Jakub Jelinek wrote:
> > > If the host has long double the same as double, sure, PTX can use its native
> > > DFmode even for long double. But otherwise, the storage must be
> > > transferable between accelerator and host.
> >
> > Hm, sorry, the 'must' is not obvious to me: is it known that the OpenMP ARB
> > would find only this implementation behavior acceptable?
>
> long double is not non-mappable type in the spec, so it is supposed to work.
> The implementation may choose not to offload whenever it sees long
> double/__float128/_Float128/_Float128x etc.
>
> > Apart from floating-point types, are there other situations where modes carry
> > information not deducible from the rest of the tree node?
>
> Dunno about fixed types, partial ints etc., but it is mostly floating point
> types, sure.
Mostly floats I guess. But just to say it would be very nice to have
enough information in the trees so layout_type can re-construct the
mode. It already does for 99% of the types... (just grep for
SET_TYPE_MODE).
Richard.
next prev parent reply other threads:[~2017-01-04 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 18:37 Alexander Monakov
2017-01-02 10:19 ` Jakub Jelinek
2017-01-02 15:39 ` Alexander Monakov
2017-01-02 15:54 ` Jakub Jelinek
2017-01-02 18:50 ` Alexander Monakov
2017-01-02 19:03 ` Jakub Jelinek
2017-01-02 19:39 ` Alexander Monakov
2017-01-02 20:24 ` Jakub Jelinek
2017-01-04 10:14 ` Richard Biener [this message]
2017-01-04 10:04 ` Richard Biener
2017-01-09 18:56 ` Alexander Monakov
2017-01-10 9:23 ` Richard Biener
2017-01-10 15:30 ` Alexander Monakov
2017-01-11 8:16 ` Richard Biener
2017-01-11 14:06 ` Alexander Monakov
2017-01-10 15:53 ` Vladislav Ivanishin
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.LSU.2.11.1701041112220.5294@t29.fhfr.qr \
--to=rguenther@suse.de \
--cc=amonakov@ispras.ru \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=vlad@ispras.ru \
/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).