whitequark[cis] changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings: Amaranth each Mon 1700 UTC, Amaranth SoC each Fri 1700 UTC · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
notgull has quit [Ping timeout: 256 seconds]
catlosgay[m] has quit [Quit: Idle timeout reached: 172800s]
lf_ has quit [Ping timeout: 256 seconds]
lf has joined #amaranth-lang
Degi_ has joined #amaranth-lang
Degi has quit [Ping timeout: 260 seconds]
Degi_ is now known as Degi
zooooooo[m] has joined #amaranth-lang
<zooooooo[m]> Has there been efforts into fuzzing amaranth as a parser? https://security.googleblog.com/2020/12/how-atheris-python-fuzzer-works.html
<whitequark[cis]> I don't think so
<_whitenotifier-e> [amaranth] whitequark commented on issue #1049: Miscompilation of nested ifs - https://github.com/amaranth-lang/amaranth/issues/1049#issuecomment-1905231649
<_whitenotifier-3> [amaranth] whitequark opened pull request #1051: back.verilog: forbid Yosys version range with dangling else bug. - https://github.com/amaranth-lang/amaranth/pull/1051
<_whitenotifier-e> [amaranth] codecov[bot] commented on pull request #1051: back.verilog: forbid Yosys version range with dangling else bug. - https://github.com/amaranth-lang/amaranth/pull/1051#issuecomment-1905264495
<cr1901> It seems that it's not possible to use amaranth-soc and amaranth-boards as dependencies in the same project: http://gopher.wdj-consulting.com:70/paste/d9041bba-31f6-47ad-9215-f3b45e14c8c1.txt Is this intentional?
<cr1901> (When dependencies = [
<cr1901> "amaranth>=0.4",
<cr1901> ], I should be clear)
<cr1901> And [tool.pdm.dev-dependencies] includes "amaranth-soc @ git+https://github.com/amaranth-lang/amaranth-soc" and "amaranth-boards @ git+https://github.com/amaranth-lang/amaranth-boards"
<cr1901> (FWIW, my solution for now is dependencies = ["amaranth @ git+https://github.com/amaranth-lang/amaranth@v0.4.1"]. That's fine for tonight.)
cr1901_ has joined #amaranth-lang
cr1901 has quit [Read error: Connection reset by peer]
<_whitenotifier-3> [rfcs] jfng commented on pull request #16: A CSR register API for amaranth-soc - https://github.com/amaranth-lang/rfcs/pull/16#issuecomment-1905618404
Darius has quit [Quit: Bye]
Darius has joined #amaranth-lang
<zignig> ls -al
<galibert[m]> .: Permission denied
<zignig> galibert[m]: wrong window ! :)
<galibert[m]> :-)
<zignig> galibert[m]: waht are you working on?
<galibert[m]> reverse-engineering the sw1000xg and the ds2416
<zignig> I have a tinybx , have a risc-v core hanging off a ftdi. it's working but there are problems....
<zignig> i've not used amaranth for some time, 0.4 is awesome, interfaces and structures.
<galibert[m]> yeah, they're really, really nice
<zignig> her quarkyness seems to be focused on WASM , good for her.. I think that a tidy tool box is the way to go.
<zignig> what is sw1000xg ?
<galibert[m]> An old yamaha synthesizer pci card
<zignig> mm nice.
<zignig> cr1901 has a microcoded core call "sentinal" and there is minerva it amaranth.
<galibert[m]> yeah, both cores are nice and I think cr's is very up-to-date with the amaranth evolutions
<zignig> both look pretty shiny, I think that back plane rather than just blinky is the way forward.
<zignig> anyway. carry on. kids need tucking in... :P
<zignig> SHAZAM, sub midgets sleeping! w00t.
<zignig> anyway.
<zignig> Catherine, thanks for your hard work. Impressed that this has not lost steam.
<zignig> Carry on.
RobTaylor[m] has joined #amaranth-lang
<RobTaylor[m]> zignig: there's also Coreblocks, which seems to be following amaranth latest changes as well
notgull has joined #amaranth-lang
zignig has quit [Quit: leaving]
zignig has joined #amaranth-lang
zignig has quit [Quit: leaving]
leptonix has quit [Quit: leaving]
leptonix has joined #amaranth-lang
notgull has quit [Ping timeout: 268 seconds]
notgull has joined #amaranth-lang
ovf_ has joined #amaranth-lang
lf_ has joined #amaranth-lang
richardeoin has joined #amaranth-lang
ovf has quit [Ping timeout: 264 seconds]
RobTaylor[m] has quit [Ping timeout: 264 seconds]
zooooooo[m] has quit [Ping timeout: 264 seconds]
lf has quit [Ping timeout: 264 seconds]
richarde1 has quit [Ping timeout: 264 seconds]
ovf_ is now known as ovf
RobTaylor[m] has joined #amaranth-lang
zooooooo[m] has joined #amaranth-lang
notgull has quit [Ping timeout: 260 seconds]
cr1901_ is now known as cr1901
cr1901 has quit [Quit: Leaving]
cr1901 has joined #amaranth-lang
<cr1901> http://gopher.wdj-consulting.com:70/paste/am-dep.zip So I created a sample project. If you swap any of the comment pyproject.toml, then run "pdm update" and "pdm test", either "pdm update" will fail, or "pdm test" will fail.
<cr1901> dependencies = ["amaranth>=0.4.1"]
<cr1901> has a InconsistentCandidate error, because amaranth-soc, even as a dev-dependency, depends on amaranth git repo
<whitequark[cis]> yep
<cr1901> So I pin the amaranth tag to the git dep, which is morally equivalent
<whitequark[cis]> amaranth-soc requires some unreleased features from amaranth
<cr1901> Okay so it's by design that "if you use amaranth-soc, you cannot release your package on PyPi at this time"
<whitequark[cis]> yes
<cr1901> Very good, that makes things easy
<cr1901> "if you use amaranth-soc, even as a dev-dep*, you cannot..." (at least pdm enforces this, have no idea what other build backends do)