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.catirclogs.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #amaranth-lang
oter has quit [Server closed connection]
oter has joined #amaranth-lang
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #amaranth-lang
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #amaranth-lang
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #amaranth-lang
d_olex_ has quit [Remote host closed the connection]
d_olex_ has joined #amaranth-lang
pie_ has quit []
pie_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #amaranth-lang
RobTaylor[m] has quit [Quit: Idle timeout reached: 172800s]
RobTaylor[m] has joined #amaranth-lang
<RobTaylor[m]> does anyone know how to stop UnusedElaboratable messages when a test fails? # amaranth: UnusedElaboratable=no at the top of the test file doesn't seem to do the job
<whitequark[cis]> probably a bug
<RobTaylor[m]> i should get my head around how that mechanism works. its still a bit of a mystery to me =)
<whitequark[cis]> grabs a backtrace, extracts the file, and checks the first few lines
<RobTaylor[m]> Catherine: btw for my own purposes, i updated amaranth-soc#58 to be current against main . Should i submit a pull request to amaranth-soc?
<whitequark[cis]> <RobTaylor[m]> does anyone know how to stop UnusedElaboratable messages when a test fails? # amaranth: UnusedElaboratable=no at the top of the test file doesn't seem to do the job
<whitequark[cis]> you might need to add src_loc_at where applicable, i don't recall if wiring.Component has it as a parameter but if it doesn't it probably should
<whitequark[cis]> RobTaylor[m]: sure
<RobTaylor[m]> whitequark[cis]: thanks, will do
<RobTaylor[m]> whitequark[cis]: i'll dig in and see whats actually going on. might be that it needs to step back though the trace
Wanda[cis] has quit [Quit: Idle timeout reached: 172800s]
<_whitenotifier-8> [amaranth] robtaylor opened pull request #1621: Modify MustUse to iterate the stack frame and collate options from all frames. - https://github.com/amaranth-lang/amaranth/pull/1621
<RobTaylor[m]> Catherine: for discussion ^ :)
<_whitenotifier-8> [amaranth] codecov[bot] commented on pull request #1621: Modify MustUse to iterate the stack frame and collate options from all frames. - https://github.com/amaranth-lang/amaranth/pull/1621#issuecomment-3137351980
<_whitenotifier-8> [amaranth-soc] robtaylor opened pull request #104: Add annotations for memory maps, wishbone and CSR primitives [updated] - https://github.com/amaranth-lang/amaranth-soc/pull/104
<_whitenotifier-8> [amaranth-soc] robtaylor reviewed pull request #58 commit - https://github.com/amaranth-lang/amaranth-soc/pull/58#discussion_r2243544453
<zyp[m]> <RobTaylor[m]> Catherine: btw for my own purposes, i updated amaranth-soc#58 to be current against main . Should i submit a pull request to amaranth-soc?
<zyp[m]> I have some proposed changes to that, but I'll need to go through what I did and compare
<RobTaylor[m]> zyp[m]: nice! Happy to have a look at your branch and integrate
frgo_ has quit [Ping timeout: 240 seconds]
frgo has joined #amaranth-lang
<zyp[m]> it's not a branch, I built against latest main and monkeypatched the changes instead: https://github.com/zyp/katsuo-bridge/tree/main/katsuo/bridge/_monkeypatch
<vup> is it intentional, that `data.Const` returns a boolean when comparing with another `data.Const`, while `_ast.Const` returns a `Operator("==", ...)`?
<vup> Furthermore, is there any reason, `data.Const` is not hashable?
frgo has quit [Remote host closed the connection]
<zyp[m]> the main change I want is the ability to attach additional annotations to a memory map, and my implementation is still half baked because we need to sort out how to do that before a memory map is frozen, ref: https://github.com/zyp/katsuo-bridge/blob/main/katsuo/bridge/_monkeypatch/amaranth_soc_memory.py#L20
frgo has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #amaranth-lang
frgo_ has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #amaranth-lang
frgo_ has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
<_whitenotifier-8> [amaranth] rroohhh opened issue #1622: Spaces in names generates invalid `RTLIL` - https://github.com/amaranth-lang/amaranth/issues/1622
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 248 seconds]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 240 seconds]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 240 seconds]
<RobTaylor[m]> <zyp[m]> it's not a branch, I built against latest main and monkeypatched the changes instead: https://github.com/zyp/katsuo-bridge/tree/main/katsuo/bridge/_monkeypatch
<RobTaylor[m]> i'll have a look asap :)
<RobTaylor[m]> <zyp[m]> the main change I want is the ability to attach additional annotations to a memory map, and my implementation is still half baked because we need to sort out how to do that before a memory map is frozen, ref: https://github.com/zyp/katsuo-bridge/blob/main/katsuo/bridge/_monkeypatch/...
<RobTaylor[m]> yeah. I'm unsure. It feels to me like there are valid reasons to attach annotations to the memory map after it has been frozen.
<RobTaylor[m]> e.g. configuration for drivers, or things like that
<zyp[m]> I don't think partially frozen makes sense, I figure we either want to freeze it later, add a way to add annotations earlier or maybe bypass the whole issue by wrapping the frozen object in another object that adds the additional annotations
<RobTaylor[m]> yep, i'm thinking more along the lines of a separate object for user annotations. Could inject its data so that as_json picks it up
<RobTaylor[m]> i haven't put much thought in yet tho 😅
<RobTaylor[m]> RobTaylor[m]: or indeed, could just be completely seperate *shrug*
<zyp[m]> while we're at it, I published https://github.com/zyp/katsuo-ila as well
<zyp[m]> it's pretty rudimentary and probably not really usable yet, but it's an example of stuff built on katsuo-bridge
<RobTaylor[m]> zyp: on a seperate line, here's what i'm doing for my annotations using pydantic: https://github.com/ChipFlow/chipflow-lib/blob/gen-sim-main/chipflow_lib/platforms/_annotate.py
<zyp[m]> ah, that's nice, I'll have to look into that
<RobTaylor[m]> zyp[m]: i'll have to have a good look, looks interesting!
<RobTaylor[m]> zyp[m]: thought you might like it :) Let me know how you get on
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #amaranth-lang
frgo has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 244 seconds]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 260 seconds]
kuku has joined #amaranth-lang
frgo has joined #amaranth-lang
kuku is now known as kuku2
kuku2 has quit [Client Quit]
frgo has quit [Ping timeout: 252 seconds]