• Bug#1068174: yosys: Please package the latest upstream release

    From Daniel =?utf-8?Q?Gr=C3=B6ber?=@21:1/5 to Scott Ashcroft on Mon Mar 17 23:30:01 2025
    Hi Scott,

    On Sun, Mar 16, 2025 at 10:06:51PM +0000, Scott Ashcroft wrote:
    (maybe we should enable those anyway?).

    The HTML docs seem to use pip to pull in some python modules (including
    one which has been forked by the yosys team) so are probably a lot more
    work than getting the pdfs building.

    Bummer. That's not worth it then. Thought it would just be a quick
    enablement thing. Thanks for looking.

    Now on to hard mode: autpkgtest. It seems debian/yosys-testsuite has lost it's precision. It runs through sucessfully but doesn't actually do anything.

    OK. That should be fixed by b3e5bef48763537e8c992150e8363ac4112d4636
    from https://salsa.debian.org/sashcroft/yosys

    Yeah that did it! Awesome.

    I think we ought to switch to applying the Makefile changes as a patch so
    we can see when upstream changes break our expectations it in the future. I don't see any real harm in just adding this to our patchstack so thats what I'll do.

    To re-use the binary .debs you already have:

    autopkgtest -B -s . -- schroot chroot:unstable-amd64-sbuild

    I say should because I couldn't figure out how to force schroot to use my yosys binary packages and stop installing the old ones from unstable.

    I had the meaning of -B wrong. It forces use of archive binaries so this
    would install yosys 0.33 instead of what we have just built. I can never
    find the right incantation to test exactly what I just built since
    autopkgtest default to just rebuilding which is annoying during
    development.

    Last time I used

    $ autopkgtest $(dcmd --deb echo ../yosys_0.49-1_amd64.changes) . -- schroot chroot:unstable-amd64-sbuild

    I just wanted to spare you the dcmd stuff.

    the end I just forced a test to fail, installed my stuff, and reran the tests.

    Hehe whatever works ;-).

    Let's see how this goes:

    Uploading to ftp-master (via ftp to ftp.upload.debian.org):
    Uploading yosys_0.49-1.dsc: done.
    Uploading yosys_0.49.orig-abc.tar.gz: done.
    Uploading yosys_0.49.orig.tar.gz: done.
    Uploading yosys_0.49-1.debian.tar.xz: done.
    Uploading yosys_0.49-1_amd64.buildinfo: done.
    Uploading yosys_0.49-1_source.changes: done.
    Successfully uploaded packages.

    Thanks,
    --Daniel

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEV6G/FbT2+ZuJ7bKf05SBrh55rPcFAmfYoLgACgkQ05SBrh55 rPc/Wg/8CNKu9twfwzfo/pT+jP5qdsxZLWf2dG7RB7CXkCz6HeCgyvoWX52+VH4S H2IS50oDr+l0qmg6laUjGgjuA1m7qrlzOlG4cPgEmt2pc+41Y+cDZWiA99bRPLvr 5rZdFtml25vi+XV98jr5fejjoMgkKXY0NXdqv4B4dwIpm7aO8olT63+afb6px7CX vls4eZ6h4lNkKNM4yFJ3geKqn10Zq58EbJ0Y0+22K3Sgq2/pJSElHMZx1DB4HgiX TnExTFfBVtKUWl1ivXBCyL+g04/Qm4tJEgkPj6BPYmRcMUTDxMZOrQGiWKNvGPei /Y8BNGoxsZgTLdROQz40zHpOBC8uIXR8sJwZVKgor38u4d4IX11sGKbTqUOTXXmo iveln2ro9qr1vtwZ3YRf2JxXJlefVA1RwzmBWCskzPbll1A1e2ibYpgBZvIyF+71 7JuLdnFwk1OsweSeYCt/IJiIkEb3zC6iwo9VMCl7MaaS8iCoKWFIqMWWPGodqucP BEHwZ69fSV2lC1B7oasQOanDZ5o1noqTdFamZaQx6ZODa11V6Q3fxhn+bjTyLUF0 ClQF4Anh/09k2qYf0PCyCDSahNZB1Fw2+ScrG+J5MBHh47foz+SGx06WZZ+5bn8S WpyoDcUHlQXiv4NmJYJDGlSLPoLmPzgeoBw8FUliXylWlScLp5Q=
    =fgDm
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniel =?utf-8?Q?Gr=C3=B6ber?=@21:1/5 to All on Tue Mar 18 00:30:01 2025
    I tried quickly building 0.51 and that seems to have yet more issues:

    /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o: in function `abc::Scl_LibertyParse(char*, int)':
    /<<PKGBUILDDIR>>/abc/src/map/scl/sclLiberty.c:563:(.text+0x41f0): undefined reference to `abc::gzopen(char const*, char const*)'
    /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o:/<<PKGBUILDDIR>>/abc/src/map/scl/sclLiberty.c:566:(.text+0x423f): undefined reference to `abc::gzread(void*, void*, unsigned int)'
    /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o:/<<PKGBUILDDIR>>/abc/src/map/scl/sclLiberty.c:575:(.text+0x4263): undefined reference to `abc::gzclose(void*)'
    collect2: error: ld returned 1 exit status

    It never ends :D

    --Daniel

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEV6G/FbT2+ZuJ7bKf05SBrh55rPcFAmfYrWUACgkQ05SBrh55 rPcz3A/9Ebo6E6cp/kr+WJySpLwBPyoqNIvonJhlt0asWVQdk6YJXiXDfU9bPkgm 7ZrWYwFBp6mfFdiNFZGexg1XQY7ihm95Ay7QIcgHkksraGQtomDFw0DVhXCSi/I1 vznsrWBl8Wpha1Zszqr7IPKhuQpJQyWwYvT50JwaEm3wL6JzJ6/hojb4dMUtKMB+ jbPeB2bPeP3452OCaEABik+hxGAnbMlqO0whweUeZhLmGouy71TZq7wVU48NY6RX OwXnsjWE7gZ5N4yML7JLQsz7w95zHdz8uWslVyXPu4DBzVGPyuwU/2A+AOiWvcPI X4FFF+EsttiL+r4nAE0iZ1Ovsll23+KWVpfZ82/QvVrcANuJeFru+lzORd9HWQ2k jP6SJo7kQubhleG05T4ikzEllN8avNE6goCVidxMWXRHGILXmhkCHARUt+AwLnZE afQDVjEbwRxjUJIyFaenz+6mpZ1UzxGJtG3T0ocvxjhg90wwC8eB/ClDds63peN/ BpU+nvqg0+UZ/58vrSJCzUXL43R1rI3rZ2N7cWXJXJeu97O+tSAnBKbtj0EALftK IoIj8qxGSOSc0s1dkqKWagAr12Qp8WDxDmOUcgRcUPCi55KHYr17lNufH88vsYqT xd5t/uueNYTYWv4xWdxyEQ5S3QR+PDg9cTuz1epAhWhU1PJ5Tk0=
    =axKs
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?ISO-8859-1?Q?Daniel_Gr=F6ber?=@21:1/5 to Scott Ashcroft on Tue Mar 18 01:40:01 2025
    On 18 March 2025 01:07:21 CET, Scott Ashcroft <scott.ashcroft@hotmail.com> wrote:
    Looks like the 32-bit builds are failing during the tests.
    Are the tests supposed to run at build time?

    Yeah thats intended.

    The armhf one seems to have run of memory.
    The i386 just fails one of the big FSM tests.
    Should we just be dropping 32-bit support?

    We've seen FST problems due to i386 floating point weirdness before (rounding, 80bit>64bit conversion IIRC). Might just be something like that again.

    Could drop 32bit or just skip tests there. I may have a quick look tomorrow and drop if its too annoying.

    --Daniel
    Hi Scott

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniel =?utf-8?Q?Gr=C3=B6ber?=@21:1/5 to Scott Ashcroft on Tue Mar 18 14:10:01 2025
    On Tue, Mar 18, 2025 at 11:19:00AM +0000, Scott Ashcroft wrote:
    On Tue, 2025-03-18 at 00:16 +0100, Daniel Gröber wrote:
    I tried quickly building 0.51 and that seems to have yet more issues:

    /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o: in function `abc::Scl_LibertyParse(char*, int)':
    /<<PKGBUILDDIR>>/abc/src/map/scl/sclLiberty.c:563:(.text+0x41f0): undefined reference to `abc::gzopen(char const*, char const*)'
    /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o:/<<PKGBUILDDIR>>/abc/src/map/scl/sclLiberty.c:566:(.text+0x423f): undefined reference to `abc::gzread(void*, void*, unsigned int)'
    /usr/bin/ld: /tmp/cc8nRSkd.ltrans73.ltrans.o:/<<PKGBUILDDIR>>/abc/src/map/scl/sclLiberty.c:575:(.text+0x4263): undefined reference to `abc::gzclose(void*)'
    collect2: error: ld returned 1 exit status

    They've added zlib support in there too. Changing the include to
    #include <zlib.h> gets the build working again.

    Aah debian/patches/abc/remove_zlib_convenience.patch just needs
    adjusting. Alright easy.

    Uploading to ftp-master (via ftp to ftp.upload.debian.org):
    Uploading yosys_0.51-1.dsc: done.
    Uploading yosys_0.51.orig-abc.tar.gz: done.
    Uploading yosys_0.51.orig.tar.gz: done.
    Uploading yosys_0.51-1.debian.tar.xz: done.
    Uploading yosys_0.51-1_amd64.buildinfo: done.
    Uploading yosys_0.51-1_source.changes: done.
    Successfully uploaded packages.

    Thanks,
    --Daniel

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEV6G/FbT2+ZuJ7bKf05SBrh55rPcFAmfZbeAACgkQ05SBrh55 rPeYLBAAsfpla334NWtbEm3F2Ybq+5iVdDRQLSL6c9M6xcDx7o7hpQtrQrzbKx2s oaXRl0AGKXR7WjCtmxNowc7rMvd1c0WYlRPbvRWiuUy16CJpWhluRqWXQiSITCfH sLluPoSuK+KY531391rr4BTsz9s07+xtOUdna6oDXCbP3+HlmRMIQ/i57wb852LM 2eyCudEsewzmbXSDjSeENOEaR7dNxUxDh9Lkln37fSrzlDSMqFTr401tLXfNp+oF O3nAx3rnGEfLa/b7sAfOgyfHwR2SqSpogdgTSzOPZN1XU9Nf73B0/I7zYJqBBrbw WlQ+VUMa+1WcSRnUbJUvOl80Q2jF5JigfyEv8+tYmUM+F30TSN2Q45FqEduDdu2H 399T5z8ulKhkafLSjdf7TI7sxuiWcBFywzAegz5XgORIk+/mClTHlLOaf8av19Vc 7FIbOb1KNETGUr/+tOGJYd2/u9Y8UmYphDjgK2WIyDzCIOx1aSAriJcKGDF99I8q hEBm6Uet8icstMySrD/7oeT7BNtWNud784OvS2av/ODi65wWIhBIk5Jf7wVHTHQA 20Yqxfg1X9uGR25xWV19GYoeFNGIwvzcLMwLMjMcYt61hWtGLwnMfMtk/Joxc7BK gaxnlkUF+vzR9hmhFeFQUJ0bD7tjNRYnalIWaD9MovNMz9FY4BI=
    =NTj4
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniel =?utf-8?Q?Gr=C3=B6ber?=@21:1/5 to Scott Ashcroft on Tue Mar 18 15:10:01 2025
    On Tue, Mar 18, 2025 at 01:51:49PM +0000, Scott Ashcroft wrote:
    On Tue, 2025-03-18 at 01:32 +0100, Daniel Gröber wrote:
    We've seen FST problems due to i386 floating point weirdness before (rounding, 80bit>64bit conversion IIRC). Might just be something like that again.

    Looks like you are spot on.
    The i386 and amd64 versions write identical FST files.
    When the i386 version tries to read back the file it has just written
    it fails trying to do an endian check on doubles.

    Commenting out the check at libs/fst/fstapi.cc:4727 makes the FST tests
    pass.
    Maybe we need to replace it with a test which says it is within a
    delta.

    Last time it just needed a strategically placed (double) cast. Idk why this would have started breaking again?

    The same code is used in gtkwave and iverilog so it looks like nobody
    cares about i386.

    Could drop 32bit or just skip tests there. I may have a quick look tomorrow and drop if its too annoying.

    If we just skip the tests then the i386 version won't be able to use
    FST files at all.

    Assuming we fix that up somehow then a bunch of other tests fail on all 32-bit archs.

    simple/string_format
    simple_abc9/string_format

    both make iverilog try to malloc huge amounts of memory. I can't tell
    if the problem is on the yosys or iverilog side of things.

    The tests in cxxrtl fail too. No floating point so I guess just a size
    of int/pointer mismatch somewhere.

    I suspect just dropping 32-bit support is going to be easiest way
    forward as the upstreams of major bits of the FPGA workflow are broken.

    Ugh, yeah, screw this. Even many embedded things have 64bit support these
    days. I don't see the use-case for yosys on 32bit. nextpnr is still working
    on i386 at least, but oh well ;-)

    I filed a ftp-master RM (removal) request for the affected arches
    ($ reportbug ftp.debian.org).

    --Daniel

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEV6G/FbT2+ZuJ7bKf05SBrh55rPcFAmfZfOgACgkQ05SBrh55 rPcJYhAAlZ5LwYOdeS/zsNL3QA5Me/1tuWc78Tkvgv3uhe2xCiCuPKSzrr3tNyK/ d73cQSAGq86q8MLgIWIAAqwv6TzYKj0BNo3/s7RM5AX9nSwSahz+lCS3qbVrn8dc Tk8j7vI2OQ464iENSvxj5u0QaQJ8DDuSTkJEpTNxyp+dVVJ81nbwsktfY/fn3Iui Bol2VIKjDg+TFJPUpuY98GTdYt+C0qvkLzcxXASz8Rk7rANT/O6WcJK/VgSrsnZj ik+XwwoisKJCRWtclNtmKxrEQpn7WBTP+MzsgB++bIQzWyVdDW0lgLC8W4ij2WVO +gu012hjRHocCLES15k8BcAGKZTUGwqJklO+8hXHHQTHTviDhXiQ3J/WynIHHYA8 B7QW9mpzP05thZSJYRT5QIl5hp/4v06mB69JXL4JiLdNzh41ukJongJWAZs0Csbf 9dA933B/3TquyoCk9Rs7DGEitBjwly99EDEQIqjEymyp1iivt4B0UIT5Zfk9hAWe yL89m5DOAnUn4z16UO7GbS8cmy81pjCPRbYQBpNekuoyz7xs6+dIdXNgViwb5wa/ DgTndGMRpjnKBFq5Gl5FrxtMXJEwG8YiWLDLB8G3EaOJc4d5av/qP1aTuTvlPCa0 ajRbfQJH6ACPOH9fAUt+H+14jZsbG/3ifkiEITQAi2S8sGtWzec=
    =/Q/U
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)