fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
fengling_ has joined #m-labs
key2 has quit [Ping timeout: 250 seconds]
sb0 has quit [Quit: Leaving]
FelixVi has joined #m-labs
rohitksingh_work has joined #m-labs
sb0 has joined #m-labs
FelixVi has quit [Remote host closed the connection]
<
sb0>
bb-m-labs, force build artiq-kc705-nist_qc2
<
bb-m-labs>
build forced [ETA 24m19s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
GitHub141>
artiq/release-1 2c749c7 Sebastien Bourdeauducq: targets/pipistrello: work around Xst placer idiocy
<
sb0>
bb-m-labs, force build --branch=release-1 artiq-pipistrello-nist_qc1
<
bb-m-labs>
build forced [ETA 30m55s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
sb0>
bb-m-labs, force build --branch=release-1 artiq
<
bb-m-labs>
build forced [ETA 34m49s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
sb0>
I will tag, build and announce 1.2 in a moment
<
GitHub147>
artiq/release-1 fe2b249 Sebastien Bourdeauducq: RELEASE_NOTES: 1.2
<
rjo>
whitequark: yes. i would relax that as well. or maybe something in python/asyncio changed making it slower.
<
sb0>
of course, the placer result that worked cannot be reproduced
<
sb0>
do we really need to keep supporting pipistrello?
<
rjo>
as long as the problems are limited to intermittent ise things i would like to keep it.
<
sb0>
I already spent 2 hours on this today, it's still not working, and there are other things like DRTIO that I'd rather do
<
rjo>
but imho we can release before we have a pipistrello build
<
sb0>
and dealing with the ISE garbage isn't exactly interesting, pleasant, or economically fruitful
<
rjo>
no. i get that. let's try to give ise a bit more room so that it doesn't choke on itself.
<
rjo>
did that build not just pass?
<
sb0>
it's still building, the problem is when it fails, it does so after 1hr30 of grinding bits
<
rjo>
ah. you checked the same thing i did.
<
sb0>
I got it to pass when manually building, by adding this -t 40 map option
<
sb0>
for some reason it doesn't work in the buildbot
<
rjo>
i'll just kill a few ttl channels, slow the clock a bit and shrink fifos.
<
sb0>
bb-m-labs, stop build artiq-pipistrello-nist_qc1
<
bb-m-labs>
try 'stop build WHICH <REASON>'
<
sb0>
bb-m-labs, stop build artiq-pipistrello-nist_qc1 ise
<
bb-m-labs>
build 237 interrupted
<
sb0>
bb-m-labs, force build --branch=release-1 artiq-pipistrello-nist_qc1
<
GitHub112>
artiq/release-1 ce73e8e Sebastien Bourdeauducq: target/pipistrello: shrink TTL FIFOs
<
bb-m-labs>
The build has been queued, I'll give a shout when it starts
<
sb0>
bb-m-labs, stop build artiq-kc705-nist_clock pipistrlllo
<
bb-m-labs>
build 541 interrupted
<
bb-m-labs>
build forced [ETA 30m55s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
sb0>
bb-m-labs, force build --branch=release-1 artiq
<
bb-m-labs>
build forced [ETA 34m49s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
rjo>
sb0: is that the application logo/icon or the one in the MDI area?
<
rjo>
sb0: how do i get into the win vm?
<
sb0>
vnc win7-experimental.lab.m-labs.hk from the internal network
<
rjo>
what's better vnc-over-an-ssh-tunnel or x11-forwarding-a-vnc-client? ;)
<
sb0>
the x11 protocol is inefficient
sb0 has quit [Quit: Leaving]
<
rjo>
why does git on that vm always fail saying 'the remote end hung up unexpectedly'?
<
GitHub17>
artiq/master f3435cf Robert Jordens: MANIFEST.in: logo*.svg (#483)
key2 has joined #m-labs
sb0 has joined #m-labs
<
sb0>
bb-m-labs, force build --branch=release-1 artiq
<
bb-m-labs>
build forced [ETA 32m10s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
sb0>
bb-m-labs, force build --branch=release-1 artiq-kc705-nist_qc1
<
bb-m-labs>
build forced [ETA 12m18s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
sb0>
bb-m-labs, force build --branch=release-1 artiq-kc705-nist_qc2
<
bb-m-labs>
The build has been queued, I'll give a shout when it starts
<
sb0>
bb-m-labs, force build --branch=release-1 artiq-pipistrello-nist_qc1
<
bb-m-labs>
The build has been queued, I'll give a shout when it starts
<
bb-m-labs>
build forced [ETA 30m11s]
<
bb-m-labs>
I'll give a shout when the build finishes
<
bb-m-labs>
build forced [ETA 26m36s]
<
bb-m-labs>
I'll give a shout when the build finishes
fengling_ has quit [Ping timeout: 240 seconds]
<
whitequark>
rjo: done
<
GitHub33>
artiq/master b6c12f2 whitequark: test: relax RPCTiming rpc_time_stddev from 1ms to 2ms....
<
rjo>
whitequark: ack. but i do wonder why on windows, that test seems to start failing now, git complains about connections, etc..
fengling_ has joined #m-labs
<
whitequark>
I vaguely recall it also failing before, though not as much
<
whitequark>
good question though
fengling_ has quit [Ping timeout: 240 seconds]
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
<
whitequark>
ugh, rust wants atomics
<
rjo>
there are l.swa and l.lda, right?
<
whitequark>
yes. but LLVM doesn't know about them.
<
GitHub160>
llvm-or1k/artiq 5817508 whitequark: [OR1K] Implement support for l.[mpc]sync instructions.
<
GitHub160>
llvm-or1k/artiq 504257d whitequark: [OR1K] Implement support for l.{lwa,swa} instructions.
<
whitequark>
but it still needs support for LLVM lowering.
<
whitequark>
since l.lwa and l.swa are just LL/SC primitives.
rohitksingh_work has quit [Read error: Connection reset by peer]
tmbinc__ has quit [Ping timeout: 276 seconds]
tmbinc__ has joined #m-labs
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
rohitksingh has joined #m-labs
jboulder has joined #m-labs
rohitksingh1 has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
fengling_ has joined #m-labs
rohitksingh1 has quit [Ping timeout: 246 seconds]
fengling_ has quit [Ping timeout: 240 seconds]
ylamarre has joined #m-labs
rohitksingh has joined #m-labs
fengling_ has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
sandeepkr has quit [Ping timeout: 240 seconds]
kuldeep has quit [Ping timeout: 246 seconds]
sandeepkr has joined #m-labs
kuldeep has joined #m-labs
ylamarre has quit [Quit: ylamarre]
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
sandeepkr_ has joined #m-labs
sandeepkr__ has joined #m-labs
sandeepkr has quit [Read error: No route to host]
sandeepkr_ has quit [Ping timeout: 240 seconds]
rohitksingh has quit [Ping timeout: 258 seconds]
rohitksingh has joined #m-labs
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
rohitksingh has quit [Quit: Leaving.]
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
<
GitHub18>
llvm-or1k/artiq 9b1e3d0 whitequark: [OR1K] Implement support for l.[mpc]sync instructions.
<
GitHub18>
llvm-or1k/artiq 8c54657 whitequark: [OR1K] Implement support for l.{lwa,swa} instructions.
<
GitHub130>
llvm-or1k/artiq 234203f whitequark: [OR1K] Implement support for l.[mpc]sync instructions.
<
GitHub130>
llvm-or1k/artiq 23beaed whitequark: [OR1K] Implement support for l.{lwa,swa} instructions.
<
GitHub130>
llvm-or1k/artiq 240f48a whitequark: Mark some FP intrinsics as safe to speculatively execute...
<
whitequark>
okay, this is very obnoxious
<
whitequark>
l.swa and l.lwa only do word accesses, and or1k can be both little and big endian depending on runtime flags
<
whitequark>
and real-world software expects that all legal memory access sizes can be done both atomically and non-atomically
<
whitequark>
so like, I'd have to emulate byte stores by masks and shifts and LL/SC loops, and if I have a byte cmpxchg that becomes completely mad
<
whitequark>
so screw that, I'll just patch rust's libcore
<
whitequark>
has anyone ever used or1k's atomics for anything useful, I wonder
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
<
GitHub8>
rust/artiq c3daa39 whitequark: Add OR1K support.
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
mumptai has joined #m-labs
<
cr1901_modern>
I wonder why byte accesses aren't supported...
kuldeep has quit [Ping timeout: 250 seconds]
sandeepkr__ has quit [Ping timeout: 240 seconds]
mumptai has quit [Quit: Verlassend]
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
fengling_ has joined #m-labs
fengling_ has quit [Ping timeout: 240 seconds]
<
altker128>
cr1901_modern: Might have been the MIPS patent on byte / unaligned access
<
altker128>
cr1901_modern: Which has also now expired.
<
whitequark>
just bad design
<
whitequark>
l.lwa doesn't even follow their own instruction encoding rules