From: "Dallman, John" <john.dallman@siemens.com>
To: dave <xdavefournier@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: making double type default to 80 or 128 bytes
Date: Fri, 7 Aug 2020 15:38:37 +0000 [thread overview]
Message-ID: <CF619CD2963921478D1D10019C667D1D0124AF7B9B@DEKOMMBX001.net.plm.eds.com> (raw)
In-Reply-To: <ddf4798f-620e-531e-8bce-b31a08dedb2a@gmail.com>
I think you mean 80 or 128 bits, surely?
> Is it possible to modify the gcc compiler so that recompiling existing code and
> libraries will produce longer doubles (80 or 128 bytes) without having to re-
> declare all the double types. This may be a stupid question but I'm looking
> for a quick fix to see if extra precision helps with an optimization problem.
This is not a quick fix. It's way more work than changing declarations in any reasonable-size program.
--
John Dallman
Nullius in verba
> -----Original Message-----
> From: Gcc-help <gcc-help-bounces@gcc.gnu.org> On Behalf Of dave via Gcc-
> help
> Sent: 07 August 2020 16:00
> To: gcc-help@gcc.gnu.org
> Subject: making double type default to 80 or 128 bytes
>
>
> Is it possible to modify the gcc compiler so that recompiling existing code and
> libraries will produce longer doubles (80 or 128 bytes)
>
> without having to re declare all the double types. This may be a stupid
> question but I'm looking for a quick fix to see if extra
>
> precision helps with an optimization problem. Thanks.
-----------------
Siemens Industry Software Limited is a limited company registered in England and Wales.
Registered number: 3476850.
Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD.
next prev parent reply other threads:[~2020-08-07 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 14:59 dave
2020-08-07 15:38 ` Dallman, John [this message]
2020-08-07 15:59 ` Dennis Clarke
2020-08-10 23:37 ` Jim Wilson
2020-08-07 18:23 ` Jonathan Wakely
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=CF619CD2963921478D1D10019C667D1D0124AF7B9B@DEKOMMBX001.net.plm.eds.com \
--to=john.dallman@siemens.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xdavefournier@gmail.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).