00:42 <vipqualitypost[m> happy new year everyone! thanks for all the hard work on this project! it's such a pleasure to use and 0.4 is very exciting!

00:46 <whitequark[cis]> happy new year

00:46 <whitequark[cis]> I'm glad you like it

03:56 <_whitenotifier-3> [YoWASP/vscode] whitequark 2876a69 - Add Python language support.

03:56 <_whitenotifier> [YoWASP/vscode] whitequark pushed 1 commit to main [+1/-1/±13] https://github.com/YoWASP/vscode/compare/d710a80f2c62...2876a69511fa

03:59 <_whitenotifier> [YoWASP/vscode] whitequark tagged 2876a69 as v0.2.0 https://github.com/YoWASP/vscode/commit/2876a69511fa657cd8836e0c1c99c28f52debaa6

03:59 <_whitenotifier> [vscode] whitequark created tag v0.2.0 - https://github.com/YoWASP/vscode

04:00 <_whitenotifier-3> [YoWASP/vscode] whitequark d81dd0a - Bump version.

04:00 <_whitenotifier> [YoWASP/vscode] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/YoWASP/vscode/compare/2876a69511fa...d81dd0a2750a

04:06 <_whitenotifier-3> [YoWASP/toolchain-demo] whitequark pushed 1 commit to main [+1/-1/±3] https://github.com/YoWASP/toolchain-demo/compare/6a1e42b1720b...23009ceacafd

04:06 <_whitenotifier> [YoWASP/toolchain-demo] whitequark 23009ce - Use Amaranth instead of Verilog.

04:09 <whitequark[cis]> check this out: https://vscode.dev/github/YoWASP/toolchain-demo

04:09 <whitequark[cis]> Amaranth, Yosys, nextpnr, and openFPGALoader running entirely in the browser

04:38 <_whitenotifier-3> [YoWASP/vscode] whitequark tagged b2654eb as v0.2.1 https://github.com/YoWASP/vscode/commit/b2654eb5d4d045af8656b6862c7bcc0e7f5ce8f9

04:38 <_whitenotifier> [vscode] whitequark created tag v0.2.1 - https://github.com/YoWASP/vscode

04:38 <_whitenotifier-3> [YoWASP/vscode] whitequark b2654eb - Don't overwrite files with identical contents.

04:38 <_whitenotifier> [YoWASP/vscode] whitequark pushed 1 commit to main [+0/-0/±2] https://github.com/YoWASP/vscode/compare/d81dd0a2750a...b2654eb5d4d0

04:55 <tpw_rules> whitequark[cis]: hi, saw you recent patreon email. wrt the debugger, does proprietary mean source-available? what's the sort of timeline on open source?

04:57 <whitequark[cis]> should be open source within 6 months or less

04:57 <tpw_rules> okay, just curious

04:58 <tpw_rules> also, do you know why the toolchain demo needs to sign into github?

04:58 <whitequark[cis]> as for the terms, I won't promise anything until those 6 months pass

04:58 <tpw_rules> what i mean on terms is will there be source code before those six months, or will it only be released in binary form

04:58 <whitequark[cis]> (a lot of my work actually does end up being open source under ISC and committed to the Yosys repo, just not the VSCode extension)

05:01 <whitequark[cis]> tpw_rules: vscode.dev cannot clone git repositories directly

05:01 <whitequark[cis]> it doesn't have a server side component and a browser cannot just clone a git repo on its own

05:01 <whitequark[cis]> not even from https:// URLs (I think the CORS headers are wrong for that?)

05:02 <tpw_rules> interesting

05:35 <_whitenotifier-3> [YoWASP/toolchain-demo] whitequark 4a4e4fd - Expand README.

05:35 <_whitenotifier> [YoWASP/toolchain-demo] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/YoWASP/toolchain-demo/compare/23009ceacafd...4a4e4fdd7873

05:36 <cr1901> Is there any docs for "adding a tool to yowasp (boolector)"? Hopefully it's not as badly-behaved as yices

05:37 <_whitenotifier-3> [toolchain-demo] whitequark closed pull request #1: Add very obvious explanations to the README to make it easier to get started - https://github.com/YoWASP/toolchain-demo/pull/1

05:37 <_whitenotifier> [toolchain-demo] whitequark commented on pull request #1: Add very obvious explanations to the README to make it easier to get started - https://github.com/YoWASP/toolchain-demo/pull/1#issuecomment-1873167725

05:37 <cr1901> (also happy new year +40mins from EST)

05:38 <whitequark[cis]> cr1901: not really; you copy an existing tool repository and try to do something similar

05:39 <tpw_rules> i need to get into formal verification...

05:39 <_whitenotifier-3> [YoWASP/toolchain-demo] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/YoWASP/toolchain-demo/compare/4a4e4fdd7873...8ad9a20950ee

05:39 <_whitenotifier> [YoWASP/toolchain-demo] whitequark 8ad9a20 - Expand README.

05:40 <_whitenotifier-3> [YoWASP/toolchain-demo] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/YoWASP/toolchain-demo/compare/8ad9a20950ee...6cf31d22dd49

05:40 <_whitenotifier> [YoWASP/toolchain-demo] whitequark 6cf31d2 - Expand README.

05:48 <cr1901> It doesn't look that bad to do since the python runtime package is already there (famous last words)?

05:50 <whitequark[cis]> it is not supposed to be very hard

06:14 <cr1901> I just thought of a good reason to have yowasp as an alternate toolchain for Sentinel; work around platform-specific toolchain bugs: https://github.com/YosysHQ/yosys/issues/4068

06:15 <whitequark[cis]> yep; if yowasp works for you on one platform it almost certainly work on another

06:17 <cr1901> Still I'd rather the platform-specific tools be fixed; AFAIK, this bug is UB that just isn't triggered on anywhere besides Windoze (I have a partial fix, but have been dealing w/ a hard drive failure, so it'll have to wait)

16:26 <cr1901> Okay, I have a working boolector on wasm... nowhere near ready for inclusion (need to submit a few patches to boolector and deps, yosys-smtbmc needs to learn about "yowasp-boolector"), but it does work: http://gopher.wdj-consulting.com:70/store/boolector

16:26 <cr1901> (Ignore the lack of suffix, it's wasm)

18:05 <cr1901> https://github.com/cr1901/yowasp-boolector Okay, that's enough for me for one day...