[llvm-dev] Are C++17 host applications supported?

[Reid Kleckner via llvm-dev]

It looks like this was added here:
https://github.com/llvm/llvm-project/commit/aa60b3fd875c3df1f23b9d4f491c08888e48d823

IIRC Abseil has a similar problem, and they chose not to support the use
case of ABI compat between TUs with different standard versions.

Personally, IMO LLVM should support this use case. I think it was a mistake
to add inline functions to Compiler.h, which is supposed to be all about
feature detection and macro definitions.

Alternatively if people want to keep things the way they are, we should
change LLVM's CMake to build with C++17 if it is supported. If the user can
link against LLVM and enable C++17, then the standard library shared by the
user and LLVM *must* have an aligned allocation function.

Either way, I don't think the user should have to do anything.

On Mon, Nov 25, 2019 at 3:04 AM Machiel van Hooren via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi,
>
> I am using the llvm libraries compiled with the C++14 standard with a
> host application that is compiled with the C++17 standard (Both on
> Windows/MSVC). I am running into an incompatibility for which I filed a
> bug report: https://bugs.llvm.org/show_bug.cgi?id=44131
>
> However, I was wondering if C++17 host applications are even supported?
>
> Regards,
>
> Machiel van Hooren
>
> _______________________________________________
> 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/20191126/528d0f06/attachment.html>