Does this have any implications for Rust on windows?
LLDB debugger is coming to Windows
11–20 of 37 posts
Re: LLDB debugger is coming to Windows
#12Earlier quoted context omitted.
I believe it's mostly people at Google pushing this feature. I don't think Apple had much of a say in it.
Oh sorry. I was under the impression that Apple was in charge of the LLVM project
No. The LLVM foundation is.
By numbers, Apple probably isn't even the largest contributor anymore (but this is just a guess based on mailing list traffic)
Re: LLDB debugger is coming to Windows
#13Earlier quoted context omitted.
I believe it's mostly people at Google pushing this feature. I don't think Apple had much of a say in it.
Oh sorry. I was under the impression that Apple was in charge of the LLVM project
The LLVM project as a whole has many contributors from many different companies working on things they care about and contributing it back to the community.
Re: LLDB debugger is coming to Windows
#14I am looking forward to the day when I can have a full Clang/LLVM environment on my Windows machines without relying on MinGW. Hopefully this year!
..and integrated in VS so you can just select Toolset = Clang :P
Re: LLDB debugger is coming to Windows
#15Does this have any implications for Rust on windows?
Minor implications, perhaps. Much of what was done to reach this point was just making LLDB not fall over miserably on Windows. Like, to compile.. Or to not crash on startup for example :)
Anyone who decides they're interested in making Rust programs debuggable with LLDB will be able to benefit from this work by not having to do it. Also a core debug loop is going to be the same on Windows no matter what programming language is being debugged. I don't know what Rust's generated code looks like, but presumably it will be able to reuse the core debug loop and symbol reading code to some extent, although it will need to deal with ABI specific differences, put in its own expression evaluator, and things like that.
TL;DR - Someone from the Rust community will still have their work cut out for them, but if they're so motivated then they at least some of the work done here will benefit them.
Re: LLDB debugger is coming to Windows
#16Earlier quoted context omitted.
Oh sorry. I was under the impression that Apple was in charge of the LLVM project
No. The LLVM foundation is. By numbers, Apple probably isn't even the largest contributor anymore (but this is just a guess based on mailing list traffic)
They probably would be if swift was open-source.
Re: LLDB debugger is coming to Windows
#17Earlier quoted context omitted.
No. The LLVM foundation is. By numbers, Apple probably isn't even the largest contributor anymore (but this is just a guess based on mailing list traffic)
They probably would be if swift was open-source.
Probably not, actually.
But it also depends on what you count. Google definitely has more people working directly on LLVM itself than Apple (At Google, they almost all work for me, and I know the numbers for Apple).
If you start to include related open source projects (like clang, etc), the numbers get closer, but then you have things like all of the Android related open source stuff that gets worked on (Renderscript), etc.
In any case, i'm not sure what the goal of any corporate measuring contest would be here. We are all friendly and working on the same open source projects. It's not about what "Google is doing" or "Apple is doing" but "what is getting done in the LLVM project".
Re: LLDB debugger is coming to Windows
#18It faces tough competition from the excellent Visual Studio debugger, but I hope they succeed. A compiler monoculture is bad.
Re: LLDB debugger is coming to Windows
#19For the curious, this will eventually integrate with Visual Studio.
ossreality: you are shadowbanned. DannyBee knows because he works on LLVM.
Re: LLDB debugger is coming to Windows
#20I am looking forward to the day when I can have a full Clang/LLVM environment on my Windows machines without relying on MinGW. Hopefully this year!
..and integrated in VS so you can just select Toolset = Clang :P
Especially with the Community Edition of VS making it really easy for pretty much anyone to get access to VS.
I like GCC and everything but I will be happy to leave it behind if I am honest. The politics are just too damn much for me these days. GCC should be about building a great compiler collection for the world but politics plays too big a part in it as seen with the whole AST debate going on again because of RMS. I just want a good compiler and standard library implementation. Between Clang/LLVM and VS Community I don't know if GCC will really have a huge place in the future for me.