From: Simon Wright <simon@pushface.org>
Subject: Re: GNAT Community 2020 (20200818-93): Big_Integer
Date: Sat, 01 Jul 2023 13:12:13 +0100 [thread overview]
Message-ID: <lyr0prq19e.fsf@pushface.org> (raw)
In-Reply-To: 55561d4b-8288-4770-a7b5-681567752ab0n@googlegroups.com
Frank Jørgen Jørgensen <fjj@itema.no> writes:
> I'm running the below program with GNAT Community 2020 (20200818-93)
> on Windows 11 Home.
> I have some problems trying to save big numbers to a file - so I
> noticed this behaviour:
> If I open Test.dat in Visual Studio Hex editor, it seems like this
> program saves this big number with a different bit pattern each time.
> Is that as expected?
> I do have some problems reading back the big numbers in my real code.
Looking at the source for Big_Integer[1] I see no trace of streaming
support; what you got streamed was the address of some allocated data
used under the hood to contain the big integer.
I don't know whether the ARM requires/expects Big_Integer to be
streamable, but I think you had every reason to expect it!
[1] https://github.com/gcc-mirror/gcc/blob/7e904d6c7f252ee947c237ed32dd43b2c248384d/gcc/ada/libgnat/a-nbnbin.ads#L171
next prev parent reply other threads:[~2023-07-01 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 19:28 GNAT Community 2020 (20200818-93): Big_Integer Frank Jørgen Jørgensen
2023-06-30 21:07 ` Dmitry A. Kazakov
2023-07-01 12:12 ` Simon Wright [this message]
2023-07-08 2:58 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox