(Possibly) a bug of Clang

Dear Sir:

I have posted a bug report of clang++:

https://bugs.llvm.org/show_bug.cgi?id=43496

It contains 2 code snippets, both of which can be compiled with GCC (7~9), but none of them can be compiled with Clang (6~8). I thought it is a bug of clang. And no one response my report until now.

Since it cannot be compiled with any modern edition of clang, I thought it is a serious bug. Could you please have a look about it?

Thanks a lot!

Wei

Hi Wei,

I have posted a bug report of clang++:

https://bugs.llvm.org/show_bug.cgi?id=43496

It contains 2 code snippets, both of which can be compiled with GCC (7~9), but none of them can be compiled with Clang (6~8). I thought it is a bug of clang. And no one response my report until now.

Since it cannot be compiled with any modern edition of clang, I thought it is a serious bug. Could you please have a look about it?

This is a Clang front-end bug (in template instantiation etc) so
cfe-dev is the right mailing list. I've added them as CC.

Here we talk about mid-end and back-end things: optimizations,
converting LLVM IR into assembly or object files for some particular
CPU etc.

Cheers.

Tim.

Hi Wei,

I have posted a bug report of clang++:

https://bugs.llvm.org/show_bug.cgi?id=43496

It contains 2 code snippets, both of which can be compiled with GCC (7~9), but none of them can be compiled with Clang (6~8). I thought it is a bug of clang. And no one response my report until now.

Since it cannot be compiled with any modern edition of clang, I thought it is a serious bug. Could you please have a look about it?

This is a Clang front-end bug (in template instantiation etc) so
cfe-dev is the right mailing list. I’ve added them as CC.

To close the loop on this, a bug has been filed for GCC:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92060