From: "Jaume Delclòs Coll" <cosa@cosarara.me>
To: 9front@9front.org
Subject: Re: [9front] Bug converting vlong to double on 32bit architectures
Date: Fri, 30 Dec 2022 17:57:53 +0100 [thread overview]
Message-ID: <4d582dae-3dab-7d83-47b2-276e3308311a@cosarara.me> (raw)
In-Reply-To: <6d3b100d-1732-efa2-f01c-728440859ba2@cosarara.me>
On 30/12/22 14:19, cosarara wrote:
> #define LLONG_MAX
> #define LLONG_MIN (-LLONG_MAX-1)
This was supposed to be
#define LLONG_MAX 0x7fffffffffffffffLL
#define LLONG_MIN (-LLONG_MAX-1)
next prev parent reply other threads:[~2022-12-30 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 13:19 cosarara
2022-12-30 16:57 ` Jaume Delclòs Coll [this message]
2022-12-30 18:32 ` cinap_lenrek
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=4d582dae-3dab-7d83-47b2-276e3308311a@cosarara.me \
--to=cosa@cosarara.me \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).