[llvm-dev] debugging installation problem

[James Y Knight via llvm-dev]

You should be using https://github.com/llvm/llvm-project/ (the new official
git repo), which contains both.

On Tue, Feb 5, 2019 at 4:30 PM Eric Christopher via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Typically yeah. Just check them out at approximately the same wall clock
> time :)
>
> -eric
>
> On Tue, Feb 5, 2019 at 1:10 PM David Callahan <david.callahan1 at live.com>
> wrote:
> >
> > Given they in separate repos, is there a way to to verify which
> revisions go together? Is it enough that the clang (shortly) after llvm in
> time?
> >
> > On 2/5/19, 1:03 PM, "Eric Christopher" <echristo at gmail.com> wrote:
> >
> >     Your clang and your llvm don't match, they're often version locked
> and
> >     you need to make sure both of them are the same-ish revision.
> >
> >     -eric
> >
> >     On Tue, Feb 5, 2019 at 12:22 PM David Callahan via llvm-dev
> >     <llvm-dev at lists.llvm.org> wrote:
> >     >
> >     > Sorry in advance for the limited details.
> >     >
> >     >
> >     >
> >     > I have a build of a recent (Monday) llvm/clang which I have
> installed in the expected way in my environment but I am getting failures
> like this;
> >     >
> >     >
> >     >
> >     > In file included from <some
> directory>/lib/clang/stable/include/x86intrin.h:29:
> >     >
> >     > In file included from <some
> directory>/lib/clang/stable/include/immintrin.h:118:
> >     >
> >     > <some directory>/lib/clang/stable/include/avx512cdintrin.h:37:20:
> error: use of undeclared identifier '__builtin_ia32_vpconflictdi_512'
> >     >
> >     >   return (__m512i) __builtin_ia32_vpconflictdi_512 ((__v8di) __A);
> >     >
> >     >                    ^
> >     >
> >     > <some directory>/lib/clang/stable/include/avx512cdintrin.h:59:20:
> error: use of undeclared identifier '__builtin_ia32_vpconflictsi_512'
> >     >
> >     >   return (__m512i) __builtin_ia32_vpconflictsi_512 ((__v16si) __A);
> >     >
> >     >                    ^
> >     >
> >     > Any suggestions on what might be messed up in the
> build/installation?
> >     >
> >     > (In other contexts I would delete all build directories and
> restart but in this workflow I know everything started from clean checkouts)
> >     >
> >     >
> >     >
> >     > Thanks for any help
> >     >
> >     > david
> >     >
> >     > _______________________________________________
> >     > LLVM Developers mailing list
> >     > llvm-dev at lists.llvm.org
> >     >
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.llvm.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fllvm-dev&data=02%7C01%7C%7C8f8a44941bf0472f473908d68bad6323%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636849974134376594&sdata=QmWltB1VgfMqJM3SnZlq9KSZ0Fl4Y16B2tQFxrAvk3I%3D&reserved=0
> >
> >
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190206/c6458ea2/attachment.html>