public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
		Ilya Verbin <iverbin@gmail.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: nvptx offloading patches [3/n], i386 bits RFD
Date: Tue, 04 Nov 2014 18:58:00 -0000	[thread overview]
Message-ID: <CAFULd4afV70SvQ7_DcAHLHG=0FbwRZ1oyRrtueWJ-ZGW8dqn-Q@mail.gmail.com> (raw)
In-Reply-To: <5458C7F8.8080702@codesourcery.com>

On Tue, Nov 4, 2014 at 1:35 PM, Bernd Schmidt <bernds@codesourcery.com> wrote:

>> Not sure how to deal with this any further out than the immediate term
>> than using a hack like this. Though I'd prefer to avoid the #ifdef as it
>> seems to me this shouldn't be baked in at build/configure time.
>
>
> Yeah, I'm not expecting the i386 part to go in quite as-is. For reference
> I'm including the offload-abi patch - Ilya is submitting this along with
> other option changes. One possibility would be to print and recognize
> strings such as lp64D128 or lp64D96 which would include information about
> the size of long double. Somehow though I can't really bring myself to
> believe that -mlong-double128 is a real use case with offloading so we might
> just disallow the combination.
>
> CCing Uros in case he has an opinion.

-mlong-double-128 was introduced for Android in:

2014-02-03  H.J. Lu  <hongjiu.lu@intel.com>

    * config/i386/i386.c (flag_opts): Add -mlong-double-128.
    (ix86_option_override_internal): Default long double to 64-bit for
    32-bit Bionic and to 128-bit for 64-bit Bionic.

    [...]

IMO, if it troubles offloading, anything else than the default
-mlong-double-80 should be disallowed.

Uros.

  reply	other threads:[~2014-11-04 18:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 11:58 nvptx offloading patches [3/n], RFD Bernd Schmidt
2014-11-03 22:28 ` Jeff Law
2014-11-04 12:38   ` nvptx offloading patches [3/n], i386 bits RFD Bernd Schmidt
2014-11-04 18:58     ` Uros Bizjak [this message]
2014-11-04 21:50     ` Jeff Law
2014-11-05  0:23       ` Bernd Schmidt
2014-11-14 18:42         ` Bernd Schmidt
2015-02-04 11:38 ` nvptx offloading patches [3/n], RFD Jakub Jelinek
2015-02-09 10:20   ` Richard Biener
2015-02-16 21:08     ` Jakub Jelinek
2015-02-16 21:35       ` Richard Biener
2015-02-16 21:44         ` Jakub Jelinek
2015-02-17 10:00           ` Richard Biener
2015-02-18 10:00             ` Jakub Jelinek
2015-02-25  8:51               ` Patch ping Jakub Jelinek
2015-02-25  9:30                 ` Richard Biener
2015-02-25 16:51                   ` Jakub Jelinek
2015-02-18  9:05           ` nvptx offloading patches [3/n], RFD Thomas Schwinge
2015-02-17 13:32       ` Ilya Verbin
2015-02-17 15:39         ` Jakub Jelinek
2015-02-17 16:21           ` Joseph Myers
2015-02-17 16:40             ` Jakub Jelinek
2015-02-18  9:12               ` Thomas Schwinge
2015-02-18 10:27                 ` Jakub Jelinek
2015-02-18 11:34                 ` Jakub Jelinek
2015-02-18 12:10                   ` Thomas Schwinge
2015-02-18 12:35                     ` Jakub Jelinek
2015-02-19 10:50                       ` If we're building an offloading compiler, always enable the LTO front end (was: nvptx offloading patches [3/n], RFD) Thomas Schwinge
2015-02-19 10:53                         ` Jakub Jelinek
2015-02-20  9:42                           ` Thomas Schwinge
2015-02-19 10:20               ` nvptx offloading patches [3/n], RFD Bernd Schmidt
2015-02-19 12:02                 ` Offloading compilers' support libraries (was: nvptx offloading patches [3/n], RFD) Thomas Schwinge
2015-02-19 12:11                   ` Offloading compilers' support libraries Bernd Schmidt
2015-02-19 12:19                     ` Thomas Schwinge
2015-02-20 15:35                       ` Ilya Verbin
2015-02-20 19:59                         ` Ilya Verbin
2015-02-26 19:35                           ` Ilya Verbin
2015-02-20  9:33                 ` Offloading compilers' libgcc installation (was: nvptx offloading patches [3/n], RFD) Thomas Schwinge
2015-02-20 19:32                   ` Ilya Verbin
2015-03-10 12:35                     ` Offloading compilers' libgcc installation Thomas Schwinge
2015-04-27 16:15                       ` Thomas Schwinge
2015-04-27 16:16                         ` Jakub Jelinek

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='CAFULd4afV70SvQ7_DcAHLHG=0FbwRZ1oyRrtueWJ-ZGW8dqn-Q@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=bernds@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=iverbin@gmail.com \
    --cc=law@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).