<d1b2>
<OmniTechnoMancer> Indeed to check how nyuzi does in a cyclone V
<d1b2>
<OmniTechnoMancer> I need*
<d1b2>
<OmniTechnoMancer> Sad to hear about RISC-V being weird about public extensions
<sorear>
public extensions are fine, they just expect projects with non-standard extensions (pulp, cheri, rocket-chip, etc) to maintain downstream gcc/binutils forks. somehow I expect the same thing to happen with the rs6000 port
<lkcl>
OmniTechnoMancers: sorear is quite correct in that it is reasonable to keep non-standard extensions "isolated" because it would destabilise and disrupt the entire RISC-V community, permanently.
<lkcl>
the bit that's sad (and weird) is that after 18 months of reasonable in-good faith requests to have a route to getting the 3D extensions "officially" proposed (rather than isolated), they systematically failed to comply with their legal obligations under Trademark Law.
<lkcl>
Lofty: that's really exciting to hear
<lkcl>
sorear: with IBM still rumbling along to get the OPF ISA WG set up, it'll be on a scale of NN months (N appx 12)
<lkcl>
it's much more likely that they'll go into a LLVM IR port (for use by Vulkan 3D) than they will go into gcc
<lkcl>
and first into binutils (gas) so we can at least write assembly code
<lkcl>
anything that goes into mainline gcc, clang-llvm and other front-ends has to have *all* OPF Members on board, the OPF Community takes the long-term stability and binary compatibility very seriously.
<lkcl>
we're talking Aerospace embedded radiation-hardened micro-controllers on the one hand, and 200 Watt IBM TFLop supercomputer processors on the other
emeb has quit [Quit: Leaving.]
<d1b2>
<OmniTechnoMancer> Ah
Degi has quit [Ping timeout: 240 seconds]
Degi has joined #nmigen
samlittlewood has quit [Ping timeout: 260 seconds]
samlittlewood has joined #nmigen
<d1b2>
<OmniTechnoMancer> Is libresoc going the larrabee style direction with 3d?
electronic_eel_ has joined #nmigen
electronic_eel has quit [Ping timeout: 272 seconds]
PyroPeter_ has joined #nmigen
PyroPeter has quit [Ping timeout: 256 seconds]
PyroPeter_ is now known as PyroPeter
emeb_mac has quit [Quit: Leaving.]
jeanthom has joined #nmigen
Asu has joined #nmigen
bob_twinkles has quit [Quit: No Ping reply in 180 seconds.]
bob_twinkles has joined #nmigen
electronic_eel_ has quit [Ping timeout: 265 seconds]
electronic_eel has joined #nmigen
happycube has quit [Ping timeout: 264 seconds]
key2 has quit [Ping timeout: 264 seconds]
key2 has joined #nmigen
happycube has joined #nmigen
jeanthom has quit [Ping timeout: 260 seconds]
chipmuenk has joined #nmigen
Shari2 has joined #nmigen
_whitelogger has joined #nmigen
electronic_eel has quit [Ping timeout: 256 seconds]
electronic_eel has joined #nmigen
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #nmigen
emeb has joined #nmigen
jeanthom has joined #nmigen
bob_twinkles has quit [Read error: Connection reset by peer]
bob_twinkles has joined #nmigen
<_whitenotifier-f>
[nmigen] anuejn opened issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuEG
<_whitenotifier-f>
[nmigen] anuejn edited issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuEG
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkuur
peeps[zen] has joined #nmigen
peepsalot has quit [Ping timeout: 264 seconds]
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkugB
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkugi
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jku2U
jeanthom has quit [Ping timeout: 240 seconds]
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jku29
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkuaq
<_whitenotifier-f>
[nmigen] whitequark edited a comment on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkuaq
chipmuenk has quit [Ping timeout: 240 seconds]
chipmuenk has joined #nmigen
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuVM
Asu has quit [Ping timeout: 240 seconds]
Shari2 has quit [Quit: Leaving]
Asu has joined #nmigen
Asu has quit [Ping timeout: 240 seconds]
Asu has joined #nmigen
jeanthom has joined #nmigen
cr1901_modern1 has joined #nmigen
emeb_mac has joined #nmigen
cr1901_modern has quit [Ping timeout: 246 seconds]
chipmuenk has quit [Quit: chipmuenk]
cr1901_modern1 has quit [Quit: Leaving.]
cr1901_modern has joined #nmigen
samlittlewood_ has joined #nmigen
samlittlewood has quit [Ping timeout: 264 seconds]
samlittlewood_ is now known as samlittlewood
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jku5o
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkudU
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkudo
jeanthom has quit [Remote host closed the connection]
<anuejn>
cr1901_modern: do you have any idea on #546 ?
jeanthom has joined #nmigen
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkud7
<cr1901_modern>
anuejn: No I've never seen anything like this
<anuejn>
sad, thanks anyway
<cr1901_modern>
Just a guess: I think the "$" needs to be escaped
<cr1901_modern>
which is what the curly braces SHOULD be doing but of course they aren't
jeanthom has quit [Ping timeout: 246 seconds]
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuAB
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuAi
<_whitenotifier-f>
[nmigen] whitequark commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuAM
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuAx
<_whitenotifier-f>
[nmigen] anuejn commented on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/Jkuxm
<_whitenotifier-f>
[nmigen] anuejn edited a comment on issue #546: platform.add_clock_constraint does not work for instances with lattice diamond for machxo2 - https://git.io/JkuAB
<_whitenotifier-f>
[nmigen] codecov[bot] edited a comment on pull request #547: vendor.lattice_machxo_2_3l: fix sdc generation - https://git.io/JkupN
<_whitenotifier-f>
[nmigen] codecov[bot] edited a comment on pull request #547: vendor.lattice_machxo_2_3l: fix sdc generation - https://git.io/JkupN
<_whitenotifier-f>
[nmigen] codecov[bot] edited a comment on pull request #547: vendor.lattice_machxo_2_3l: fix sdc generation - https://git.io/JkupN
<_whitenotifier-f>
[nmigen] codecov[bot] edited a comment on pull request #547: vendor.lattice_machxo_2_3l: fix sdc generation - https://git.io/JkupN
<agg>
just added yowasp to let my CI do actual synthesis, super slick, thanks whitequark!
<_whitenotifier-f>
[nmigen] codecov[bot] edited a comment on pull request #547: vendor.lattice_machxo_2_3l: fix sdc generation - https://git.io/JkupN
<agg>
gitlab ci lets you extract 'coverage' with a regex and can chart it and report it per run and see diffs in PRs and so on, but I wish you could extract arbitrary data, like LUTs used, or max clock, and chart those instead...