[llvm-bugs] [Bug 33951] New: New Pass Manager does not always use -pass-remarks-output

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Jul 26 11:11:27 PDT 2017


            Bug ID: 33951
           Summary: New Pass Manager does not always use
           Product: new-bugs
           Version: unspecified
          Hardware: Macintosh
                OS: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: ashe2 at cs.washington.edu
                CC: llvm-bugs at lists.llvm.org

When trying to use the `-pass-remarks-output` flag with the new pass manager,
it doesn't always work.

Using `opt <input> -passes='require<opt-remark-emit>,...' -pass-remarks='.*'
-pass-remarks-output=<remark_file> -o <output>`, the
`-pass-remarks-output=<remark_file>` is only sometimes used, based on its

- if `-pass-remarks-output=-` is passed, then the yaml is printed to stdout, as
it should be.
- if `-pass-remarks-output=<remark_file>` is passed, then that file is not
created, and no yaml is printed into it.

In all of these cases, using the old pass manager (ie, `opt -inline` or
similar), then the `-pass-remarks-output=...` option does indeed print to
either stdout or the given filename.

I can provide patches for some of the opt remark tests which show this failing
only with the new pass manager.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170726/6a8af960/attachment.html>

More information about the llvm-bugs mailing list