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 · play https://amaranth-lang.org/play/ · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
Maja_ has quit [Ping timeout: 272 seconds]
Maja has joined #amaranth-lang
Degi_ has joined #amaranth-lang
Degi has quit [Ping timeout: 264 seconds]
Degi_ is now known as Degi
Stary has quit [Quit: ZNC - http://znc.in]
Stary has joined #amaranth-lang
frgo has joined #amaranth-lang
frgo_ has quit [Read error: Connection reset by peer]
notgull has joined #amaranth-lang
notgull has quit [Ping timeout: 264 seconds]
notgull has joined #amaranth-lang
notgull has quit [Ping timeout: 264 seconds]
marcan has quit [Quit: Now where's my screwdriver...]
marcan has joined #amaranth-lang
balrog has quit [Ping timeout: 268 seconds]
balrog has joined #amaranth-lang
<_whitenotifier-9> [yosys] qarlosalberto commented on issue #24: Error when used with VSCode and Teroshdl - https://github.com/YoWASP/yosys/issues/24#issuecomment-2120488465
cr1901_ is now known as cr1901
<_whitenotifier-9> [yosys] whitequark commented on issue #24: Error when used with VSCode and Teroshdl - https://github.com/YoWASP/yosys/issues/24#issuecomment-2120723865
<whitequark[cis]> there's no meeting today
zyp[m] has joined #amaranth-lang
<zyp[m]> time to write some more RFCs so we've got something to discuss :)
<zyp[m]> (or finish, in my case, for the fixedpoint one)
<whitequark[cis]> that would be good
<whitequark[cis]> also I think my feedback on #66 is unaddressed still?
<_whitenotifier-9> [yosys] qarlosalberto commented on issue #24: Error when used with VSCode and Teroshdl - https://github.com/YoWASP/yosys/issues/24#issuecomment-2120742436
<_whitenotifier-9> [yosys] whitequark commented on issue #24: Error when used with VSCode and Teroshdl - https://github.com/YoWASP/yosys/issues/24#issuecomment-2120749601
<_whitenotifier-9> [yosys] qarlosalberto commented on issue #24: Error when used with VSCode and Teroshdl - https://github.com/YoWASP/yosys/issues/24#issuecomment-2120751295
<_whitenotifier-9> [YoWASP/clang] whitequark pushed 1 commit to main [+6/-0/±0] https://github.com/YoWASP/clang/compare/93cab50b4714...089a32b847f2
<_whitenotifier-9> [YoWASP/clang] whitequark 089a32b - Initial commit.
<zyp[m]> <whitequark[cis]> "specifically https://github.com..." <- oh, yeah, sounds good, I figured we'd bikeshed where to put it at the meeting
<whitequark[cis]> I've actually been avoiding nominating it since that's unresolved
<whitequark[cis]> and it would need an update to say exactly which APIs get added a new type option
<zyp[m]> fair enough
<zyp[m]> I have a slight concern that add_clock_constraint currently takes an int or float frequency, and depending on whether the platform constraint format takes a frequency or a period might not need a round trip through the reciprocal period at all, so we'd potentially be introducing a rounding error where there's none today
<whitequark[cis]> I don't think that matters
<whitequark[cis]> a timing constraint is not an exact limit but it has PVT variation and some safety margin on top anyway
<whitequark[cis]> all of those make rounding errors irrelevant
<zyp[m]> all negligible, of course, so I won't lose any sleep over it, just remarking
<whitequark[cis]> it would potentially matter for eg a PLL
<whitequark[cis]> but I think those use periods usually
<zyp[m]> the PLLs I've worked with just takes division factors and the rest is calculated from the input clock
<whitequark[cis]> I think the complex ones usually have the toolchain calculate the factors
Wanda[cis] has joined #amaranth-lang
<Wanda[cis]> PLLs often take the input frequency in addition to the factors
<Wanda[cis]> to optimize some internal loop filter parameters or whatever
<Wanda[cis]> (tbh I don't really know how any of this works, I just reverse engineer bitstreams)
<_whitenotifier-9> [clang] whitequark created branch wasmtime-issue-8652 - https://github.com/YoWASP/clang
<_whitenotifier-9> [amaranth] whitequark reviewed pull request #1355 commit - https://github.com/amaranth-lang/amaranth/pull/1355#discussion_r1607105745
<_whitenotifier-9> [amaranth] whitequark reviewed pull request #1355 commit - https://github.com/amaranth-lang/amaranth/pull/1355#discussion_r1607105208
<_whitenotifier-9> [amaranth] whitequark reviewed pull request #1355 commit - https://github.com/amaranth-lang/amaranth/pull/1355#discussion_r1607107175
jfng[m] has joined #amaranth-lang
<jfng[m]> how can i document the signature of a component that doesn't have its own `Signature` class ?
<jfng[m]> i see that a "Members" section is used in the latter case (https://amaranth-lang.org/docs/amaranth/latest/stdlib/memory.html#amaranth.lib.memory.WritePort.Signature)
<jfng[m]> otoh, `lib.crc` uses "Attributes" (https://amaranth-lang.org/docs/amaranth/latest/stdlib/crc.html#amaranth.lib.crc.Processor)
<whitequark[cis]> isn't it holiday today
<jfng[m]> it seems awkward to me to talk about signature members in one case, and attributes in the other
<jfng[m]> it is
<whitequark[cis]> lib.crc is outdated, I only recently added Members
<whitequark[cis]> you can submit a PR to switch Attributes to Members. previously Sphinx would break
<whitequark[cis]> there's some stuff in conf.py to make it not break on this type of section
<jfng[m]> ok
notgull has joined #amaranth-lang
notgull has quit [Ping timeout: 264 seconds]
<jfng[m]> <whitequark[cis]> "you can submit a PR to switch..." <- actually, to do it properly, when would have to port `lib.crc` to components, and it is tempting to port the rest of stdlib too (except maybe `lib.coding` because it is going away)
<jfng[m]> but then `lib.fifo` is a bit weird; the `FIFOInterface` mixin is public API and would have to go away
<whitequark[cis]> that would require an RFC first
<jfng[m]> s/when/one/
<jfng[m]> yeah..
<whitequark[cis]> and yes it should use Attributes until it's a component
<whitequark[cis]> I forgot that it wasn't
<_whitenotifier-9> [amaranth] whitequark closed issue #1047: Tracking issue for RFC 30: Component metadata - https://github.com/amaranth-lang/amaranth/issues/1047
<_whitenotifier-9> [amaranth] wanda-phi reviewed pull request #1355 commit - https://github.com/amaranth-lang/amaranth/pull/1355#discussion_r1607200440
<_whitenotifier-9> [amaranth] whitequark opened pull request #1362: pyproject: use pdm-backend~=2.3.0 - https://github.com/amaranth-lang/amaranth/pull/1362
<_whitenotifier-9> [amaranth] whitequark reviewed pull request #1355 commit - https://github.com/amaranth-lang/amaranth/pull/1355#discussion_r1607209975
<_whitenotifier-9> [amaranth] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-1362-c1666adf30666b8a07839253361602e9e0e10344 - https://github.com/amaranth-lang/amaranth
<_whitenotifier-9> [amaranth-lang/amaranth] github-merge-queue[bot] pushed 1 commit to main [+0/-0/±1] https://github.com/amaranth-lang/amaranth/compare/c1666adf3066...e2b47c1a9ea3
<_whitenotifier-9> [amaranth-lang/amaranth] whitequark e2b47c1 - pyproject: use pdm-backend~=2.3.0.
<_whitenotifier-9> [amaranth] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-1362-c1666adf30666b8a07839253361602e9e0e10344 - https://github.com/amaranth-lang/amaranth
<_whitenotifier-9> [amaranth] whitequark closed pull request #1362: pyproject: use pdm-backend~=2.3.0 - https://github.com/amaranth-lang/amaranth/pull/1362
<_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] whitequark pushed 1 commit to main [+0/-0/±39] https://github.com/amaranth-lang/amaranth-lang.github.io/compare/34cd8eca8c1d...facc373bce94
<_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] github-merge-queue[bot] facc373 - Deploying to main from @ amaranth-lang/amaranth@e2b47c1a9ea319f8165d00363768654f85d23eb1 🚀
<whitequark[cis]> Wanda: hm, have we deprecated `Pin`?
<Wanda[cis]> there's an outstanding pr
<whitequark[cis]> ohhh, I see
<whitequark[cis]> (I'm writing the documentation page at the moment)
<Wanda[cis]> also you wanted to block that on docs?
<Wanda[cis]> right
nyanotech has quit [Remote host closed the connection]
nyanotech has joined #amaranth-lang
<cr1901> https://github.com/amaranth-lang/amaranth/pull/1344/files#diff-dd63cd2d6f49ad56727a18503ed07510277983d2fb437fa842ff0077e56a33acR54 Does this mean coro-based testbenches are supported, or is this a compat wrapper to be deprecated when e.g. 0.5/0.6 is released?
<cr1901> generator-based* testbenches not coro... bleh
lf has quit [Ping timeout: 240 seconds]
lf has joined #amaranth-lang
<cr1901> https://github.com/cr1901/pytest-amaranth-sim/compare/async pytest plugin has been updated for async testbench functions