Opened 2 years ago

Closed 2 years ago

#16207 closed enhancement (fixed)

asymptote-2.80

Reported by: Bruce Dubbs Owned by: ken@…
Priority: normal Milestone: 11.2
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description (last modified by ken@…)

New minor version (was 2.79)

Change History (13)

comment:1 by ken@…, 2 years ago

I suggest we let this stew until TL2023 has finished its pretest.

comment:2 by Douglas R. Reno, 2 years ago

Summary: asymptote-2.79asymptote-2.79 (Wait until TL2022)

comment:3 by Bruce Dubbs, 2 years ago

Milestone: 11.299-Waiting

comment:4 by ken@…, 2 years ago

Description: modified (diff)
Milestone: 99-Waiting11.2
Owner: changed from blfs-book to ken@…
Status: newassigned
Summary: asymptote-2.79 (Wait until TL2022)asymptote-2.80

279 -

The transparency shader was further optimized. The tensorshade fillrule was fixed. A compatibility fix was made to xasyBezierInterface.py. A real operator ecast(rational r) was implemented up to maxDenominator=100000. The dvisvgmMultipleFiles option, which speeds up xasy deconstruction with PDF TeX engines, was documented.

280 -

Release Notes for Version 2.80 Compression of empty transparent pixel counts and other optimizations were implemented in the transparency shader. A weighted least-squares fit was added.

comment:5 by ken@…, 2 years ago

I find 280 useless. My latex-test-20220322 'cylinder' test to create a PDF puts the loadavg over 8 on this 8-core box, but eventually completes. However, the PDF does not contain the graphic, only the heading label. Using my asy-test-20200809 tarball the tests to create webgl (rotateable html) work but tests to create pdf, png and svg files fail, reporting

util_cpu_caps.num_cpu_mask_bits = 32

shipout3(prefix,f,preview ? nativeformat() : format,

/opt/texlive/2022/texmf-dist/asymptote/three.asy: 2896.13: runtime:

I suspect that the binary 2022 release doesn't contain asy-280, will need to find a spare machine to check that.

in reply to:  5 comment:6 by ken@…, 2 years ago

Replying to ken@…:

I find 280 useless. My latex-test-20220322 'cylinder' test to create a PDF puts the loadavg over 8 on this 8-core box, but eventually completes. However, the PDF does not contain the graphic, only the heading label. Using my asy-test-20200809 tarball the tests to create webgl (rotateable html) work but tests to create pdf, png and svg files fail, reporting

util_cpu_caps.num_cpu_mask_bits = 32

shipout3(prefix,f,preview ? nativeformat() : format,

/opt/texlive/2022/texmf-dist/asymptote/three.asy: 2896.13: runtime:

I suspect that the binary 2022 release doesn't contain asy-280, will need to find a spare machine to check that.

I now suspect this is again a "doesn't work on amdgpu" problem. 280 is being used by debian (sid) and gentoo, and it works on my skylake (intel video, I suppose the iris driver in mesa).

I'll need to review what I've used in the recent past on amdgpu (if anything).

comment:7 by ken@…, 2 years ago

Definitely an amdgpu problem. I've uploaded a new simplified set of tests in asy-cylinder.tar.gz to https://www.linuxfromscratch.org/~ken/asy-cylinder-tests/ with explanation in the README file in that directory.

Although this doesn't test the old 2D output from asy, it provides a much shorter test of the 3D functions.

With the new reduced tests, on BLFS-11.1 without CFLAGS on my picasso (3400G) with current amdgpu firmware (partially updated in February 2022 according to git blame) and linux-5.17.1 it now creates output for each of the tests, without overloading the cores, but for the pdf, png and svg targets the output is just a white background and for the latex test only the heading appears. Both 2.78 and 2.79 do not have any problem.

Now, when the output is blank I get a series of messages each saying:

amdgpu: Failed to allocate a buffer: amdgpu: size : 4135129088 bytes amdgpu: alignment : 2097152 bytes amdgpu: domains : 4 amdgpu: flags : 4

(11 of these for the pdf target, similar for png, only 4 for svg). The latex target does not appear to produce any odd onscreen messages. But each of these failures creates a syslog message:

[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered

Requires firmware updates on my normal (hardened) system on the picasso to see if that too now completes, and testing on my renoir.

Works ok on skylake with 2.80.

comment:8 by ken@…, 2 years ago

No progress on the picasso.

Issue raised for 2.80, https://github.com/vectorgraphics/asymptote/issues/312 proceding with 2.79 which works ok on all my machines.

comment:9 by ken@…, 2 years ago

Updated to 2.79 in 845db20de8c21cf09090e55a39be7e45c7b48296 11.1-429

Keeping open re 2.80 pending any feedback on the issue I've raised.

comment:10 by ken@…, 2 years ago

Milestone: 11.299-Waiting

comment:11 by ken@…, 2 years ago

I thought there was a fix in the git version I was asked to test. Worked fine on my minimal asy-cylinder tests. I backported that to 2.80, same. But then I started on my fuller asy-test-20200809.tar.xz tests for random kleinbottles. Fails with a shipot3 runtme error.

Went back to that git version, similar. Issue 313 opened, because I'd closed the original :-(

comment:12 by ken@…, 2 years ago

Milestone: 99-Waiting11.2

Further fix committed upstream (also applies to 2.79 on this machine).

comment:13 by ken@…, 2 years ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.