[llvm-dev] How to get CLang array alloca alignments to be smaller than 16 bytes?
Don Hinton via llvm-dev
llvm-dev at lists.llvm.org
Sun May 5 14:56:42 PDT 2019
I'm sure there are people that use the XCode generator, but I develop on a
Mac and don't use it -- well, I did try it once and was underwhelmed by
what it produced and gave up on it. So, I just use Ninja, which is fast
and works great. Also, since it seems like a lot of people use it, it's
well tested, and you don't have the issues you're having with XCode. Plus
it works the some on the other platforms I use, e.g., Linux.
I do use the XCode debugger from time to time -- just setup an external
project and it figures everything out.
On Sun, May 5, 2019 at 2:24 PM Joan Lluch via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> To be honest, I don’t either know what really happens under the hood when
> CMake creates the xCode project for CLang+LLVM. But there’s something
> really *explicit* going on there, because the project as it’s shown in
> xCode does not have the same file grouping structure than the actual
> physical folders. Not only the project file grouping doesn't match the
> physical folder locations, but the group naming is different and generally
> more convenient and organised than the actual folder structure. What does
> all that, I have no idea, but cmake creates it all by just selecting xCode
> as the cmake “generator”.
> On 5 May 2019, at 22:58, Tim Northover <t.p.northover at gmail.com> wrote:
> On Sun, 5 May 2019 at 21:49, Joan Lluch <joan.lluch at icloud.com> wrote:
> However, I now have found that for some reason the .h files in the
> lib/Basic/Targets directory were not included as part of the Xcode project.
> Ah. At least we now have a common view on the source, and hopefully
> you can see what needs doing (even if Xcode won't reflect reality
> properly for whatever reason).
> I assume this is a bug on one of the cmake install files.
> As far as I'm aware LLVM has little to no Xcode magic in its CMake
> files. So the bug would be in either CMake (supplying inadequate
> dependencies?) or Xcode (misinterpreting CMake output?).
> I'm afraid I don't really know enough about either to say which is
> responsible. It could even be LLVM, though from what I *have* seen of
> CMake, I'd be surprised if we needed to declare headers.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev