https://github.com/georgthegreat closed
https://github.com/llvm/llvm-project/pull/80443
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
georgthegreat wrote:
@ldionne, gentle ping
https://github.com/llvm/llvm-project/pull/80443
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
georgthegreat wrote:
@ldionne, gentle ping
https://github.com/llvm/llvm-project/pull/80443
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
georgthegreat wrote:
@ldionne, do you find @arichardson reasoning good enough to proceed with
merging this PR?
https://github.com/llvm/llvm-project/pull/80443
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
georgthegreat wrote:
I am OK with fixing this particular guarantee with a test.
However, I am not familiar with libc++ testset organization and I need to be
guided.
Could you, please, provide me with some clues to start wtih?
https://github.com/llvm/llvm-project/pull/80443
georgthegreat wrote:
I understand the _this will definitely break in the future without proper
testing_, but libunwind does not experience frequent changes, so this might be
a working soluiton even without explicit testing.
https://github.com/llvm/llvm-project/pull/80443
georgthegreat wrote:
We have pretty large codebase and we use custom command-graph based build
system (consider bazel as a well-known example of such buld system). The system
uses module as a basic unit, modules might depend one each other, dependencies
might affect dependant modules (but not
https://github.com/georgthegreat created
https://github.com/llvm/llvm-project/pull/80443
We store libunwind code inside monorepo and would like to reduce the overall
amount of `-I` flags.
>From 3e8bbe318ebbd498a7457afee2192c47650b6dad Mon Sep 17 00:00:00 2001
From: Yuriy Chernyshov
Date: