riff-IRC has quit [Remote host closed the connection]
riff_IRC has joined #riscv
riff_IRC has quit [Read error: Connection reset by peer]
riff_IRC has joined #riscv
jerS_ has joined #riscv
riff_IRC has quit [Read error: Connection reset by peer]
jerS_ has quit [Quit: Lost terminal]
<ssb>
dh`, it was a qemu linux-user bug in waitid()
<ssb>
and it happens only on riscv32 because there it is the only wait syscall. In other targets I tested (alpha, riscv64) different code path in glibc is triggered.
FL4SHK has quit [Ping timeout: 256 seconds]
milkylainen has quit [Ping timeout: 256 seconds]
jjido has joined #riscv
FL4SHK has joined #riscv
BOKALDO has quit [Quit: Leaving]
bauruine has joined #riscv
nun has quit [Ping timeout: 240 seconds]
milkylainen has joined #riscv
milkylainen has left #riscv [#riscv]
<dh`>
yeah, I didn't want to know. glibc--
<dh`>
:-|
<ssb>
no why? no bug in glibc )
<ssb>
I'd guess it would fail in the same way with other libcs
jjido has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
pecastro has joined #riscv
EchelonX has joined #riscv
avoidr has quit [Quit: leaving]
avoidr has joined #riscv
bauruine has quit [Ping timeout: 240 seconds]
jellydonut has quit [Quit: jellydonut]
gudenau[m] has quit [Quit: You have been kicked for being idle]
___nick___ has joined #riscv
radu242407821 has quit [Ping timeout: 250 seconds]
iooi has quit [Ping timeout: 260 seconds]
iooi has joined #riscv
jjido has joined #riscv
jellydonut has joined #riscv
jjido has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
nelmire has joined #riscv
winterflaw has joined #riscv
jacklsw has quit [Ping timeout: 256 seconds]
kaph_ has joined #riscv
kaph has quit [Ping timeout: 256 seconds]
bauruine has joined #riscv
jerS_ has joined #riscv
jerS_ has quit [Client Quit]
jerS_ has joined #riscv
jerS_ has quit [Client Quit]
pabs3 has quit [Ping timeout: 240 seconds]
avoidr has quit [Quit: leaving]
pabs3 has joined #riscv
aerkiaga has joined #riscv
avoidr has joined #riscv
cousteau has joined #riscv
<cousteau>
Hi!
<gordonDrogon>
cousteau, morning.
<cousteau>
Are there plans to have a K extension ("Krypto")? Or are crypto-related instruction groups being named Zk* and Zbk* for informative purposes only, and not because the "K" is meaningful as an extension name?
<cousteau>
I've noticed that Z<letter>* sub-extensions are usually related to the <Letter> extension, not sure if that's an "official" pattern...
<cousteau>
e.g. the Zfinx extension is related to the F (and D) extension, the Zbc extension is related to B, etc
<dh`>
ssb: because paths like that shouldn't be machine-dependent
jjido has joined #riscv
BOKALDO has joined #riscv
Maylay_ has quit [Quit: Pipe Terminated]
Maylay has joined #riscv
riff-IRC has joined #riscv
riff-IRC has quit [Remote host closed the connection]
riff-IRC has joined #riscv
orionwl is now known as laanwj
irl25519 has joined #riscv
jjido has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
jjido has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
aerkiaga has quit [Remote host closed the connection]
<gordonDrogon>
hmph. emulating RV-32I BGEU on a system with a language with only signed integers is less elegant than I think it ought to be...
geranim0 has joined #riscv
drmpeg has quit [Ping timeout: 240 seconds]
<jrtc27>
just add 2^31 to each?
<jrtc27>
signed vs unsigned in two's complement just changes where the discontinuity is
jacklsw has joined #riscv
radu242407821 has joined #riscv
drmpeg has joined #riscv
radu242407821 has quit [Ping timeout: 256 seconds]
<gordonDrogon>
yes.
jjido has joined #riscv
<gordonDrogon>
implemneting RV-32IM, once insturction at a time ;-)
<gordonDrogon>
sort of surprised at how little instructions it really needs - using a small C program to test - the C compiled to 595 instructions with -O0 and 194 instructions with -O3
BOKALDO has joined #riscv
<ssb>
dh`, sure that would be great. Life is different though, system call interface required to carry old and misdesigned cruft for compatibility reasons. And is not compatible itself between 32/64 bit variants of same architecture, let alone different ports.
jellydonut has quit [Quit: jellydonut]
jtdowney has quit [Quit: Bye]
radu242407821 has joined #riscv
jtdowney has joined #riscv
radu242407821 has quit [Ping timeout: 240 seconds]
jellydonut has joined #riscv
kaph_ has quit [Ping timeout: 250 seconds]
kaph has joined #riscv
motherfsck has joined #riscv
<la_mettrie>
different sources seem to give contradicting answers to how many addressing modes risc-v has. answers have varied in range 1-4
<la_mettrie>
hm, it's possible that different sources also have a bit different ideas about what addressing mode means...