[PATCH] D134267: [C++] [Modules] Support one phase compilation model for named modules

Chuanqi Xu via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Wed Oct 19 20:38:40 PDT 2022


ChuanqiXu added a comment.

I grepped `options.td` and got (incomplete) list for options to take a output name:

  # -o and its alias
  -o
  -object_file_name=
  --output=
  
  /Fa (windows for assembly output filename)
  /Fe (windows for output executable file name)
  /Fi (windows for preprocessed output filename)
  /Fo (Windows for object file)
  
  -dependency-dot (for DOT-formatted header dependencies)
  -dependency-file (to write dependency output to)
  
  -header-include-file (Filename to write header include output to)
  
  -opt-record-file (Filename to use for YAML optimization record output)
  
  -split-dwarf-output (Filename to use for split dwarf debug info output)
  
  -stack-usage-file (to write stack usage output to)
  -coverage-data-file (Emit coverage data to this filename)
  -coverage-notes-file (Emit coverage notes to this filename)

And it looks like the `-file` appears a lot. So may be the suggestion (`-fc++-module-file-output`) may be better. And for the default location, I feel like my explanation above makes sense. If the end user wants to produce .pcm files, they can use `--precompile` just like what they do with `-c` to get the object files. This only matters with end users since the build systems should/would chose other positions.


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

https://reviews.llvm.org/D134267



More information about the cfe-commits mailing list