From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: henri.cloetens@blueice.be
Cc: gcc-help@gcc.gnu.org
Subject: Re: Bytes of long double - trouble . . .
Date: Wed, 8 Feb 2023 11:12:29 +0000 [thread overview]
Message-ID: <CAH6eHdR79H49_5NT00cF_Bf1VA5hHjT9BOmYf9CQuwVDuK6=yw@mail.gmail.com> (raw)
In-Reply-To: <20230208100922.Horde.E80Kc__Nr8RUMRxBbPIGDXo@webmail.blueice.be>
On Wed, 8 Feb 2023 at 09:10, <henri.cloetens@blueice.be> wrote:
>
> Dear Sergey, добрий ден !
>
> This is most likely because, on the machine you are using,
> the type long double is emulated in software, and the way it is
> emulated is different in both versions.
I think the most likely is x86 vs x86-64.
next prev parent reply other threads:[~2023-02-08 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 8:48 Sergey Smith
2023-02-08 9:09 ` henri.cloetens
2023-02-08 11:12 ` Jonathan Wakely [this message]
2023-02-08 11:11 ` Jonathan Wakely
2023-02-15 12:50 ` Dennis Clarke
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='CAH6eHdR79H49_5NT00cF_Bf1VA5hHjT9BOmYf9CQuwVDuK6=yw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=henri.cloetens@blueice.be \
/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).