4,368 karma · joined December 2, 2012
Reach me at keno@juliacomputing.com
http://marc.info/?t=149861183900003&r=1&w=2 http://marc.info/?t=149864742900002&r=1&w=2
Oh and the one that got fixed:
Julia is an exciting new language in the increasingly important field of mathematical computing. As machine learning becomes part of every programmer’s stack of tools, increasing demands are being put on programming languages and compilers to meet the need of simple and efficient mathematical computing. Julia Computing, one of the top contributors to the open source Julia programming language, is seeking compiler and systems engineers to take the julia programming language and its tooling to the next level.
We work at all levels of the software stack, from the hardware up, in order to support julia and its applications. Any experience working at the kernel (Linux primarily), toolchain, compiler, language, or developer tooling level, would be highly beneficial. Since tasks often span a significant range of this stack, interest in and the willingness to learn about the rest of the stack are required.
Knowledge of or previous experience with Julia is not required, but would be beneficial. However, experience working with systems-level tools (C/C++/Rust/GDB/perf etc) would be highly desirable.
Substantial portions of this work will involve contributions back to existing open source projects (Julia/LLVM/Linux, libraries, etc.) or the development of new open source projects.
Example tasks may include:
- Working with the core language team on future versions of the julia programming language
(Don't like something about the language? Here's your chance to fix it!)
- Supporting and enhancing the performance of julia HPC applications at petascale and beyond
(Obsessed about performance? Us too! Come play with supercomputers)
- Enabling julia on next-generation hardware architectures and accelerators
(Like fancy new hardware? Want to play with it before everyone else? Can do!)
- Developing modern developer tooling (debuggers, profilers, static analysis/verification tools)
(Think you can do better than the state of the art here? Come try it out!)
- Enhancing the compile-time performance of julia and the underlying LLVM compiler
(Cut down the iteration time for scientist using julia - help them come up with new ways to cure cancer, solve climate change or survey the sky faster)
- Developing novel programming models for diverse kinds of hardware
(What's the best way to program all these crazy architectures? We don't know yet, but we're planning to find out - maybe you have the crucial idea)
Both senior and junior full-time positions are available. This advertisement
is for our Boston, MA, USA location. There are no formal education requirements.
We are happy to sponsor US visas.If this position interests you, or you have any questions, please contact us at jobs@juliacomputing.com
With ever wider SIMD units this is actually happening to some extent. With AVX512 (e.g. on KNL) you can do 64 operations (single precision FLOPs) in vector units in the same amount of time as you can do 1 scalar operation. Combined with the low clock speed of the KNL, you really don't want to be doing scalar operations if you care at all about performance. Of course SIMD isn't the same as VLIW, since the operation you're doing has to be the same in all vector lanes, but with masking support in AVX512, it is getting a little closer to that.
Also compilers have gotten quite a bit smarter and with hardware die shrinks taking longer, I wouldn't be at all surprised if VLIW ISAs were to make a comeback. I guess the Itanium was a bit ahead of its time.
I met commissioner Pai in person last year (he was meeting with groups of founders in the Boston area). IIRC, the primary point of discussion was wireless spectrum policy and ensuring access to broadband internet for the greatest number of people, so I have little insight to offer into his thinking on other issues. However, in my impression he seemed to be a thoroughly decent and knowledgable person who cared deeply about the work that he is doing. I think it is important to separate the policy issues from the person.
Hope that helps. Your deployment is larger than ours, so there may be other techniques, but that's what we did.