https://bugs.llvm.org/show_bug.cgi?id=33670
Bug ID: 33670
Summary: -foptimization-record-file= should imply
-fsave-optimization-record
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Driver
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
The Clang option -foptimization-record-file= controls which file an
optimization record is output to. Optimization records are output if you use
the Clang option -fsave-optimization-record. If you specify the first option
without the second, you get a warning that the command line argument was
unused:
$ clang -fprofile-sample-use=foo.profdat -foptimization-record-file=foo.yaml
foo.c
clang-5.0: warning: argument unused during compilation:
'-foptimization-record-file=foo.yaml' [-Wunused-command-line-argument]
Should -foptimization-record-file= imply -fsave-optimization-record? It seems
like a user that specifies a custom path to an optimization record file
certainly wants Clang to output the file in the first place.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
[email protected]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
