6 ms·
Bizarre that he thinks a language or compiler is doomed unless it can compile itself on each platform it supports. Microcontrollers and cross-compilation wouldn
by naasking 7y ago
Bizarre that he thinks a language or compiler is doomed unless it can compile itself on each platform it supports. Microcontrollers and cross-compilation wouldn't exist if that were the case.
- aidenn0 7y agoI think it was more the implication that requiring more than 2GB of RAM to compile itself was an indication of its profligate resource usage.
- qppo 7y agoHow much of that is Indicative of rustc vs llvm? The latter isn't exact a lightweight piece of software.
- aidenn0 7y agoUntil there is a rustc in production that doesn't use llvm to emit code in the backend, the point is moot, no?
- adrianN 7y agoNo, I don't think so. If LLVM is at fault then the issue is definitely not inherent to Rust the language or Rust the development culture.
- kzrdude 7y agoInteresting point. Does anyone know how much memory is needed to compile llvm+clang? GCC?
- anthk 7y agoIDK about compiling llvm/clang, but using clang/llvm needs far less memory than gcc. I've used clang in machines with less than 256mb of RAM.
- saagarjha 7y agoThat varies widely on your linker and how many threads you use. I have compiled LLVM on systems with 4 GB of RAM, though; but have been forced to fall back on single-threaded compilation.
- numbsafari 7y agoYour code is what it depends on. If you are picking dependencies with no concern for the overhead they introduce, well, it says everything it needs to say: you value that dependency over the associated overhead it introduces. Asking an OS to adopt those same preferences, without any appreciation for their needs or preferences is pretty rude and arrogant. A better solution would be to ask “what would it take, because I’d like to understand your needs”. Maybe then Theo could help you understand their constraints. Trying to argue with him that he needs something he clearly doesn’t isn’t very nice and won’t get a nice response if you push it too far.
- ddevault 7y agoYou are ultimately responsible for your dependencies. No program is innocent of its dependency graph.
- qppo 7y agoTo me the question is moot if the problem is llvm. I don't know if that's the case or not. Modern tools require modern hardware. If the problem is that the target constraints don't allow modern tools to be used, the problem is the constraints and not the tools. But maybe I just don't understand their stance here.
- thesuperbigfrog 7y agoDepending on what you are working on / with, you may not be able to choose your constraints. Constraints that you cannot change can certainly dictate what tools you have to choose from.
- asveikau 7y agoIt seems like a number of *BSD projects are generally in favor of llvm and clang, in part because they dislike GNU/FSF. I know OpenBSD supports some more esoteric hardware that LLVM probably will not target, however.
- acdha 7y agoThat doesn’t seem like an especially strong argument since computing is full of time/space trade-offs and 2GB of RAM hasn’t been a significant amount for over a decade at this point (X86-64 only goes back to 2003 but it was a latecomer following Intel’s epic failure to deliver Itanium). Things like whole program optimization seem like a reasonable trade off for <$20 worth of RAM.
- ben_bai 7y agoWell OpenBSD has this "dumb" rule that snapshots/releases are never cross compiled and be done on real hardware. So it's pretty much a rule that every hardware platform has to be self hosting. Microcontrollers are the exception, but then they don't run a full blown OpenBSD stack anyways.
- fluffything 7y agoThis rule is not just dumb, it is retarded. I maintain a quite popular open source project, and OpenBSD maintains a fork. They try to submit patches every now and then, but every time it happens, I ask them to please also submit a test that makes CI fail without the patch, and pass with it. They can't, so OpenBSD remains unsupported. The problem is that there isn't a supported cross-compilation toolchain from any major platform to OpenBSD (due to this dumb rule), so if they want to compile and run the test, they need to compile a big project under qemu-system and then run the test, which is super slow. Other targets just cross-compile natively in seconds, and just run the test under qemu-user, which is super fast. So we break OpenBSD a lot, and they need to put in a lot of effort into maintaining their own fork, which takes them resources away from doing other more useful things. Adding OpenBSD code is pointless, because we can't even test that it compiles, much less works. This rule of not supporting cross-compilation hurts them more than it helps them, but it's their own fault.
- Arch-TK 7y agoI don't know what project this is but a blanket "add a test which fails without your patch for EVERY PATCH no exception" rule is a bit cargo-culty. Especially since the kind of test you're asking for, when written by a developer who is less than passionate about writing such a test but rather more passionate about just solving the problem his patch addresses, is probably not going to be worth much compared to a properly thought out set of tests which target the class of problems which the patch solves. Or possibly even an adjustment to existing tests on the basis of what the patch solves. Finally, surely you get plenty of patches which do small useful things like cleanup but which it would likely be impossible to write a test for.