<Amanieu>
Yea, you need to update the GCC and cranelift backends too.
<Amanieu>
I think ./x.py check will make sure they compile.
<cr1901>
Oops
re_irc has quit [Remote host closed the connection]
re_irc has joined #rust-embedded
<agg>
Amanieu: could you try leaving and re-joining this room to see if it helps the irc bridge? sorry for the trouble...
Amanieu has left #rust-embedded [#rust-embedded]
Amanieu has joined #rust-embedded
<Amanieu>
test
<agg>
it seems to have made a puppet for you on matrix but the puppet isn't in the matrix room...
<agg>
no joy :/
<agg>
hifi: any idea what could be going on with heisenbridge? @irc_libera_amanieu:psion.agg.io seems to exist on matrix and the name is pilled when mentioned here, but they're not in #rust-embedded:matrix.org user list and none of the messages make it through
<agg>
but it works OK for everyone else it seems
<agg>
restarting heisenbridge hasn't helped, and I can't kick that user since they're already not in the room
dreamcat4 has quit [Quit: Connection closed for inactivity]
<cr1901>
Why won't Libera add this channel to their official bridge?
<agg>
it's a mess
<agg>
you can join it through the official bridge at #rust-embedded:libera.chat from matrix actually
<Amanieu>
Should I try reconnecting to libera?
<agg>
but, all the matrix users are in #rust-embedded:matrix.org, which is a different room; the new official libera bridge can't bring an existing matrix room into irc afaik
MatrixTravelerbo has joined #rust-embedded
<agg>
Amanieu: you could try but I don't think the bridge would see that any different to you leaving this channel so I don't think it would make a difference...
matrixbridge has joined #rust-embedded
matrixbridge has left #rust-embedded [#rust-embedded]
<agg>
cr1901: and then the second problem: we still don't own this channel on the libera side because it needs someone from rust core to register #rust namespace with them and delegate #rust-embedded to us, as we had on freenode
<cr1901>
Ahhh, and presumably Freenode was before everyone on upstream Rust became allergic to IRC?
<agg>
well we asked them to do it then too and they did
<agg>
I'll try pinging core again
<agg>
ping sent
<cr1901>
tyvm
GenTooMan has quit [Ping timeout: 250 seconds]
GenTooMan has joined #rust-embedded
<re_irc>
<@hifi:vi.fi> agg I think you've not updated the bridge for like 6 months, hard to say anymore as a lot has changed
<re_irc>
<@hifi:vi.fi> also there were issues with Dendrite originally
<re_irc>
<@adamgreig:matrix.org> Heh. I updated to the latest version with python 3.7 support a few days ago to see if it would help but no difference
<re_irc>
<@adamgreig:matrix.org> Anything I can do to purge the current matrix user and force it to remake it?
<re_irc>
<@hifi:vi.fi> the major change that could make a difference was the next version
<re_irc>
<@adamgreig:matrix.org> 1.7.1 iirc
<re_irc>
<@hifi:vi.fi> there's a good chance it works with 3.7 anyway
<re_irc>
<@adamgreig:matrix.org> Pip won't let me install it from pypi but I will try and force its hand and if not I'll install a newer python
<re_irc>
<@adamgreig:matrix.org> Thanks for the tip
<re_irc>
<@hifi:vi.fi> but I think the real issue is with Dendrite as if restarting doesn't help its lying to the bridge 😅
<re_irc>
<@adamgreig:matrix.org> I could believe it... I'll give that a kick too.
emerent has quit [Ping timeout: 250 seconds]
emerent has joined #rust-embedded
<re_irc>
<@hifi:vi.fi> since the latest version is using mautrix it's more likely to work with Dendrite as I don't remember anyone complaining any mautrix bridge but working with it
<re_irc>
<@yuhanliin:matrix.org> cr1901: Does your PR support doing arithmetic/bitwise instructions directly on memory locations (like in `msp430-atomic`)?
<cr1901>
yuhanliin: No, that's beyond the scope of rust inline asm
<cr1901>
Meaning until something that supports directly operating on memory locations is supported, there's gonna be a small size penalty for atomics
<cr1901>
Still far superior to refcell/cell dance tho
<cr1901>
Yuhanliin: If you're asking "can rust inline asm, especially msp430, access memory locations?", then: yes, yes it can. And I already adapted msp430-atomic to the new syntax, and tested a deployed firmware
<cr1901>
Everything's working fine aside from the 50 byte or so size penalty