[clang] Suppress noreturn warning if last statement in a function is a throw (PR #145166)

alexfh wrote: Something went wrong here, since valid code started triggering the `-Winvalid-noreturn` diagnostic after this commit: https://gcc.godbolt.org/z/zvs9MG7rz ``` template struct S { void f(); }; template void S::f() { throw 0; } template<> void S::f() {} ``` ``` :10:19: error: fun

[clang] [llvm] [mlir] [debuginfo][coro] Emit debug info labels for coroutine resume points (PR #141937)

alexfh wrote: This patch causes a clang crash (reproducible at least up 7bf439d2607e636ada7e0bafda0fae447ec36002). Reduced test case: https://gcc.godbolt.org/z/xdnWzP9qs https://github.com/llvm/llvm-project/pull/141937 ___ cfe-commits mailing list cf

[clang] [llvm] [mlir] [debuginfo][coro] Emit debug info labels for coroutine resume points (PR #141937)

alexfh wrote: > @alexfh what makes you think this was introduced by this commit? I found this commit using a mechanical bisection over a range of LLVM revisions building Clang without assertions. So the assertion may actually be caused by a different commit. @bgra8 posted a more focused test c

[clang] Suppress noreturn warning if last statement in a function is a throw (PR #145166)

alexfh wrote: > Just out of curiosity, could implementing this warning to be LTO only solve > this? Anything requiring whole-program analysis sounds like a task to be done > during LTO. IIRC GCC has some warnings that are only made possible by LTO. I don't think this would be the right directi

[clang] Revert "[Clang] Do not treat Foo -> const Foo conversion sequences as perfect" (PR #149272)

https://github.com/alexfh approved this pull request. https://github.com/llvm/llvm-project/pull/149272 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

<    15   16   17   18   19   20