21:36 <bl0x[m]> I'm trying to synthesize some code with large Memory blocks with the Vivado tool chain. It used to infer block RAM, but with the most recent Amaranth it does not. Did something change in that regard since Amaranth 0.4.dev60? Is there a way to annotate that Is want the Memory to be block RAM?

21:37 <bl0x[m]> Vivado version is 2022.2.

21:39 <whitequark[cis]> please post a minimal complete example demonstrating the issue

21:39 <whitequark[cis]> the memory-related code was essentially completely rewritten

21:41 <bl0x[m]> I was hoping for some vague pointer... I'll see if I can produce a minimal example that shows the same issue.

21:42 <whitequark[cis]> there wouldn't be one

21:42 <whitequark[cis]> a pointer, I mean. too many changes

21:47 <bl0x[m]> I went through the change log and that was a bit too vague.

21:48 <whitequark[cis]> you won't find a single specific change responsible, no

21:48 <whitequark[cis]> even if you narrow it down to a specific commit that wouldn't help

21:53 <bl0x[m]> Ok, I'll check for myself and if I'm still lost I'll post an example

21:53 <bl0x[m]> Thanks

22:34 <bl0x[m]> I can pinpoint the change in behavior to commit 8c4a15ab. This is no surprise, I guess.

22:41 <Wanda[cis]> hmmm

22:41 <Wanda[cis]> that's actually somewhat surprising

22:42 <Wanda[cis]> that shouldn't really change what yosys emits in the end

22:42 <Wanda[cis]> well, not materially

22:46 <whitequark[cis]> famous last words