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]
<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
<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?
<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*