johnt15

4 ms·

1.
by johnt15 8y ago
It's interesting that the roadmap of volt has been saying v1.0 is just around the corner for the past half year. The other roadmap items also don't change much. https://web.archive.org/web/20180615121501/
2.
by johnt15 8y ago
Looks like EdgeRouter X fits my requirements and is pretty cheap (50Eur). Thank you!
3.
by johnt15 8y ago
Are there any routers supported by OpenWrt that can handle 1Gbps WAN to LAN? My current router only pulls 150Mbps and I want to keep OpenWrt due to the amount of custom network configuration that has been done.
4.
by johnt15 8y ago
It works fine on OSX 10.12.6. You need the following customizations (not sure what's in OSX-KVM already): - tell explicitly it's a "Penryl" CPU (<model fallback='allow'>Penryl</model>) - force
5.
by johnt15 8y ago
I can second that!
6.
by johnt15 8y ago
> or LGPL (also requires project to be LGPL) This is not correct. LGPL only requires that Qt is linked as shared libraries and sources of any changes to the Qt itself is provided.
7.
by johnt15 9y ago
Some anecdotal data: Due to some reasons I couldn't use contact lenses in one eye for a couple of months. I switched to using contacts in single eye for that period, as I can't stand glasses for more than one hour due to very high
8.
by johnt15 9y ago
Any large project needs a build system with complex data structures to express all the dependencies just due to sheer amount of them. Add various types of source generation, tooling, non-trivial build steps and simple build systems quickly
9.
by johnt15 10y ago
It's possible to work around the restriction easily. This tool ( https://github.com/p12tic/eagle-brd-merge ) can move a single Eagle board around, so whenever you want to move a component outside the allowed window
10.
by johnt15 10y ago
It's possible to do automatically this by using a SIMD library such as libsimdpp ( https://github.com/p12tic/libsimdpp ). Everything is mostly abstracted away and you just write the SIMDified code once and add a CMa
11.
by johnt15 11y ago
By saying single code path, I don't mean single instruction stream. libsimdpp, for example, supports building same code for different instruction sets, linking into the same executable and then dispatching dynamically. Doing this by ha
12.
by johnt15 11y ago
There is entire high-lever scientific computing framework built using a SIMD wrapper: https://github.com/jfalcou/nt2 . Though I must note in this case the SIMD wrapper has significant problems. Due certain design decisi
13.
by johnt15 11y ago
The property of AVX and AVX2 you mentioned actually helps having single code path. If the SIMD wrapper allows parameterization on vector width (most do that), you can simply increase vector width when compiling for AVX and that's it.
14.
by johnt15 11y ago
It's much better to use any of the numerous SIMD wrappers such as libsimdpp or Vc and get various benefits for free. It's possible to target everything from SSE and NEON to AVX512 with what is essentially a single code path.