[llvm] Solve llvm-dwp overflow problem, skipped over 4GB '.dwo' files (PR #71902)

[Jinjie Huang via llvm-commits]

Labman-001 wrote:

> Probably need some terminology to disambiguate between the current default "stop" behavior which is to abort/error/fail, and the new flag behavior of "bail out and emit a best-effort DWP".

I think this could be described as a 'soft stop' (or Graceful Stop), as opposed to the current default 'hard stop' (Abortive Stop).

> (that said, I'd still ask whether this is the right tool to add at all - I know it's a complicated space for all of us hitting these limits, so I'm not ruling anything out for sure, but trying to reduce all these different slices as much as we can - could you build less code in your situation? Or modify your build system to drop certain debug info to keep the dwp under these limits?)

The business scenario we are dealing with involves a large number of different projects all experiencing overflow issues. We are indeed considering modifying our build system to generate DWP only for the DWO parts we are interested in.
However, currently, supporting the dynamic selection of DWO for different business requirements makes solving this issue complex and difficult. At present, we indeed need a solution similar to this  kind of 'soft stop' approach.


https://github.com/llvm/llvm-project/pull/71902