Hi Ed,
> assumes char is signed... and, indeed, this seems to fix it:
Thanks, I have updated the Debian package and uploaded a new
version. Let us see how it works out.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX
The pattern of failures certainly looks like that of a program that
assumes char is signed... and, indeed, this seems to fix it:
- In io.web, change the return type of get() and peek() from char to int.
- In scan.web, change the type of prev_char, curr_char and next_char
from char to int.
Hi,
> "make check" has runaway memory usage on arm64
We can also see this on the Reproducible Builds project arm64
machines, eg.
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/3dldf_2.0.3+dfsg-5.rbuild.log
Regards,
--
,''`.
: :' : Chris Lamb
`.
Package: 3dldf
Version: 2.0.3+dfsg-2
Severity: important
This might be related to #759696, not sure.
On arm64, I just killed the build of 3dldf when I saw that a test
process using 48GB of memory. The build log around this said:
V2:
point: (4.679370, 0.00, 0.506930)
FIG:
18
V2:
point:
4 matches
Mail list logo