Earlier quoted context omitted.
Yeah it seems like most of the responses are against this proposal For casual readers, it's a proposal, not something decided
Sure, but it's a proposal from Andrew Kelley, the language creator, and it's got a bunch of thought-out subitems that seem to have real progress being made. It seems more likely than not that this will come to pass, unless the community reaction really is heavily against.
File for divorce from LLVM
11–20 of 167 posts
Re: File for divorce from LLVM
#12Every time I hear about LLVM, it turns into a rant. Clearly there is a problem there that needs to be fixed. Maybe the LLVM project team should address those issues.
As someone who works on an LLVM-based compiler at $DayJob and also has written a compiler front-end that uses LLVM in my free time, I do have a ton of gripes, but any time I feel particularly frustrated by them, I spend a little bit of time working on my non-LLVM backend. After a few days of angry swearing with little to show for it, I go back to working with LLVM with a much greater appreciation for what it's giving me.
Re: File for divorce from LLVM
#13Earlier quoted context omitted.
Sure, but it's a proposal from Andrew Kelley, the language creator, and it's got a bunch of thought-out subitems that seem to have real progress being made. It seems more likely than not that this will come to pass, unless the community reaction really is heavily against.
I mean, one of the checkboxes under LLVM is literally "optimization passes", so... I don't know how close they are to the end goal in terms of progress actually
Re: File for divorce from LLVM
#14Re: File for divorce from LLVM
#15Re: File for divorce from LLVM
#16It's your language so do whatever you want but please adjust the branding accordingly...
Re: File for divorce from LLVM
#17Earlier quoted context omitted.
Yeah it seems like most of the responses are against this proposal For casual readers, it's a proposal, not something decided
Sure, but it's a proposal from Andrew Kelley, the language creator, and it's got a bunch of thought-out subitems that seem to have real progress being made. It seems more likely than not that this will come to pass, unless the community reaction really is heavily against.
The sub-items of this task are still valuable to complete even if this overarching proposal were declined. Most of them are not being completed as a prerequisite for this proposal. There are benefits gained even without the full removal of LLVM.
I can really respect the really wide-reaching views and goals of Andrew with zig and in proposals like this, even if I don't agree.
Re: File for divorce from LLVM
#18With the amount Zig promoted being able to use it to compile c (and maybe c++ I forget) only to decide no LLVM at all seems wild. Without a LOT more people chipping in to support the odds of even coming close to the platform support of LLVM seems incredibly unlikely as well. I would understand planning to add another backend of their own for those who want that, but just getting rid of LLVM seems... rash?
Re: File for divorce from LLVM
#19Re: File for divorce from LLVM
#20Every time I hear about LLVM, it turns into a rant. Clearly there is a problem there that needs to be fixed. Maybe the LLVM project team should address those issues.
1. Needing to support tons of different platforms with various different documented and undocumented behaviours
2. Needing to support many languages with specifically undefined behaviour.
Trying to bridge the undefined nature of the two sides means that things can be fragile. Assumptions that worked for one set of undefined problems may not work for another.
But so much depends on LLVM these days that I can’t think of it as anything but a success. A flawed success but one that is doing its best to bring order to a naturally chaotic problem space.
GCC and MSVC have similar problems because it’s inherent to the problem space. So while it’s frustrating hitting those bugs, everyone in the space knows they aren’t fundamental issues with the project itself.