rjo has quit [Ping timeout: 246 seconds]
rjo has joined #m-labs
cedric has quit [Ping timeout: 250 seconds]
cedric has joined #m-labs
cedric has quit [Changing host]
cedric has joined #m-labs
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined #m-labs
rohitksingh_work has joined #m-labs
proteusguy has quit [Ping timeout: 250 seconds]
proteusguy has joined #m-labs
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_wor1 has quit [Client Quit]
rohitksingh_work has quit [Ping timeout: 268 seconds]
_whitelogger has joined #m-labs
m4ssi has joined #m-labs
m4ssi has quit [Ping timeout: 252 seconds]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
m4ssi has joined #m-labs
plonk has quit [Ping timeout: 252 seconds]
proteusguy has quit [Ping timeout: 252 seconds]
proteusguy has joined #m-labs
rohitksingh has quit [Ping timeout: 244 seconds]
rohitksingh has joined #m-labs
plonk has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh_ has joined #m-labs
sb0 has joined #m-labs
<
sb0>
key2: are there plans to implement multiplication/division (M) and compressed instructions (C) in minerva?
<
sb0>
it seems upstream rust wants that
cedric has quit [Ping timeout: 246 seconds]
<
key2>
(M) at least
<
key2>
(C) is needed ?
<
key2>
C should not be needed
<
key2>
there is no valid reason why rust would need C particularely
<
whitequark>
it's probably a target option in LLVM
<
key2>
yep, at least it doesnt really make sense to enforce C in particular
<
key2>
for "M", multiplication is 3 lines, so easy to implement
<
key2>
division would take a bit more time
<
key2>
but first, JF was focusing on getting the build system of nmigen done
<
whitequark>
i think even M should not be a hard requirement
<
ZirconiumX>
RISC-V?
<
key2>
@ZirconiumX minerva is a nmigen written riscv
<
ZirconiumX>
The current targets for that are RV32IMAC and RV32IMC; I think RV64GC is "in the works", but yeah
<
ZirconiumX>
Huh, I was considering that.
<
whitequark>
key2: sb0: yes, you do not need M or C
<
whitequark>
you need to write a JSON file with this contents and use -m,-c,... instead of +m,+c,...
<
whitequark>
and then rebuild libcore
<
ZirconiumX>
Or just a target file
<
whitequark>
that's a target file.
<
ZirconiumX>
Good thing cargo-xbuild can automate the process
<
key2>
waiting for whitequark to review/commit the PR
<
sb0>
whitequark: it's not just rebuild libcore, rustc needs to be rebuilt
m4ssi has quit [Remote host closed the connection]
<
whitequark>
sb0: why?
rohitksingh_ has quit [Remote host closed the connection]
rohitksingh has joined #m-labs
<
ZirconiumX>
No, you don't need to rebuild rustc; rustc is a cross-compiler
<
ZirconiumX>
You do need to rebuild compiler-builtins though I think
<
ZirconiumX>
Again; cargo-xbuild takes care of this stuff
proteusguy has quit [Ping timeout: 264 seconds]
<
sb0>
ffs the android build environment is more bloated than vivado
<
whitequark>
android development is extremely bad on every level
<
whitequark>
and it's getting worse over time
<
sb0>
whitequark: you need an entry in src/librustc_target/spec/mod.rs as well, otherwise rustc will reject your -target flag
<
sb0>
anyway, I got it to work
<
sb0>
(rustc, not android. android just spews out all sort of obscure errors)
<
whitequark>
sb0: no you don't, you can provide any json file in the -target option
<
sb0>
what about sailfishos, is it also trash?
<
whitequark>
what are you trying to achieve?
proteusguy has joined #m-labs
<
sb0>
get less crappy software on my phone, i.e. up-to-date and without vendor adware and other junk
<
whitequark>
does lineageos work on your phone?
<
whitequark>
that's what i've been using for like a decade at this point
<
whitequark>
well, no, 6-7 years
<
sb0>
it's somewhat hard to find a supported phone with up-to-date binary builds, so, I was wondering if building other ROMs was an option
<
sb0>
but as it turns out, it just downloaded 55GB of crap that doesn't work
<
whitequark>
yes, that's my experience in general, it's extremely finicky
<
whitequark>
i would expect that on sailfish most android applications will not broken
<
whitequark>
*will be broken
<
whitequark>
so you couldn't use whatsapp or wechat or whatever
m4ssi has joined #m-labs
esden has quit [Read error: Connection reset by peer]
esden has joined #m-labs
proteusguy has quit [Ping timeout: 250 seconds]
mauz555 has joined #m-labs
m4ssi has quit [Remote host closed the connection]
cr1901_modern has quit [Ping timeout: 245 seconds]
cr1901_modern has joined #m-labs
zng_ has joined #m-labs
zng has quit [Ping timeout: 250 seconds]
zng_ has quit [Ping timeout: 255 seconds]
zng has joined #m-labs