[PATCH] D81525: [Support] Initialize outs() errs() nulls() once

James Henderson via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Wed Jun 10 02:08:58 PDT 2020


jhenderson added a comment.

Certainly, if we go back to the old behaviour (i.e. not tied by default) it would mostly solve both issues (but see question below). It would however make it up to individual tools to opt-in to the tied behaviour, which seems like it would be wanted all over the place (basically any tool from llvm-dwarfdump to clang that use `errs()` for reporting errors and `outs()` for other information in whatever form).

That being said, is there an issue even if we change the default that somebody could manually tie `errs()` to `outs()`? The user has to make sure the initialisation order is either amenable, or that they have untied things before destruction occurs.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D81525/new/

https://reviews.llvm.org/D81525





More information about the llvm-commits mailing list