mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-04-30 01:56:06 +00:00
Code Issues Projects Releases Wiki Activity
llvm-project/llvm/test/tools/llvm-remarkutil/empty-file.test

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

23 lines
1.4 KiB
Plaintext
Raw Normal View History

[llvm-remarkutil] Add an option to print out function sizes This adds an `instruction-count` command to llvm-remarkutil. ``` llvm-remarkutil instruction-count --parser=<bitstream|yaml> <file> ``` This will, for now, only print out asm-printer `InstructionCount` remarks. Frequently I need to find out things like "what are the top 10 largest functions" in a given project. This makes it so we can find that information quickly and easily from any format of remarks. I chose a CSV because I usually want to stick these into a spreadsheet, and the data is two-dimensional. In the future, we may want to change this to another format if we add more complicated data. Differential Revision: https://reviews.llvm.org/D134765
2022-09-27 14:26:37 -07:00
RUN: not llvm-remarkutil yaml2bitstream %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --check-prefix=YAMLPARSER
RUN: not llvm-remarkutil instruction-count --parser=yaml %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --check-prefix=YAMLPARSER
Recommit "Add an option to print out annotation remark count." Add missing new line for `llvm/docs/CommandGuide/llvm-remarkutil.rst` This reverts commit 0f7fcb4c670fbef2c25b835fdfdd29598c6c13ae.
2023-04-07 23:42:39 +01:00
RUN: not llvm-remarkutil annotation-count --parser=yaml --annotation-type=remark %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --check-prefix=YAMLPARSER
[Remarks] Introduce count subcommand for llvm-remarkutil. (#66214) This tool is a generic remark counter reporting count based on specified properties. The counter can be used to count remarks individually and filter them based on name, type and pass or count using remark arguments.
2023-10-12 16:03:39 +01:00
RUN: not llvm-remarkutil count --parser=yaml %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --check-prefix=YAMLPARSER
Add a utility for converting between different types of remarks This adds llvm-remarkutil. This is intended to be a general tool for doing stuff with/to remark files. This patch gives it the following powers: * `bitstream2yaml` - To convert bitstream remarks to YAML * `yaml2bitstream` - To convert YAML remarks to bitstream remarks These are both implemented as subcommands, like `llvm-remarkutil bitstream2yaml <input_file> -o -` I ran into an issue where I had some bitstream remarks coming from CI, and I wanted to be able to do stuff with them (e.g. visualize them). But then I noticed we didn't have any tooling for doing that, so I decided to write this thing. Being able to output YAML as a start seemed like a good idea, since it would allow people to reuse any tooling they may have written based around YAML remarks. Hopefully it can grow into a more featureful remark utility. :) Currently there are is an outstanding performance issue (see the TODO) with the bitstream2yaml case. I decided that I'd keep the tool small to start with and have the yaml2bitstream and bitstream2yaml cases be symmetric. Also I moved the remarks documentation to its own header because it seems a little out of place with "basic commands" and "developer tools"; it's really kind of its own thing. Differential Revision: https://reviews.llvm.org/D133646
2022-09-09 19:58:02 -07:00
RUN: llvm-remarkutil bitstream2yaml %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --allow-empty --check-prefix=BITSTREAM2YAML
[llvm-remarkutil] Add an option to print out function sizes This adds an `instruction-count` command to llvm-remarkutil. ``` llvm-remarkutil instruction-count --parser=<bitstream|yaml> <file> ``` This will, for now, only print out asm-printer `InstructionCount` remarks. Frequently I need to find out things like "what are the top 10 largest functions" in a given project. This makes it so we can find that information quickly and easily from any format of remarks. I chose a CSV because I usually want to stick these into a spreadsheet, and the data is two-dimensional. In the future, we may want to change this to another format if we add more complicated data. Differential Revision: https://reviews.llvm.org/D134765
2022-09-27 14:26:37 -07:00
RUN: llvm-remarkutil instruction-count --parser=bitstream %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --allow-empty --check-prefix=SIZEBITSTREAM
Recommit "Add an option to print out annotation remark count." Add missing new line for `llvm/docs/CommandGuide/llvm-remarkutil.rst` This reverts commit 0f7fcb4c670fbef2c25b835fdfdd29598c6c13ae.
2023-04-07 23:42:39 +01:00
RUN: llvm-remarkutil annotation-count --parser=bitstream --annotation-type=remark %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --allow-empty --check-prefix=ANNOTATIONBITSTREAM
[Remarks] Introduce count subcommand for llvm-remarkutil. (#66214) This tool is a generic remark counter reporting count based on specified properties. The counter can be used to count remarks individually and filter them based on name, type and pass or count using remark arguments.
2023-10-12 16:03:39 +01:00
RUN: llvm-remarkutil count --parser=bitstream %p/Inputs/empty-file -o - 2>&1 | FileCheck %s --allow-empty --check-prefix=COUNTBITSTREAM
Add a utility for converting between different types of remarks This adds llvm-remarkutil. This is intended to be a general tool for doing stuff with/to remark files. This patch gives it the following powers: * `bitstream2yaml` - To convert bitstream remarks to YAML * `yaml2bitstream` - To convert YAML remarks to bitstream remarks These are both implemented as subcommands, like `llvm-remarkutil bitstream2yaml <input_file> -o -` I ran into an issue where I had some bitstream remarks coming from CI, and I wanted to be able to do stuff with them (e.g. visualize them). But then I noticed we didn't have any tooling for doing that, so I decided to write this thing. Being able to output YAML as a start seemed like a good idea, since it would allow people to reuse any tooling they may have written based around YAML remarks. Hopefully it can grow into a more featureful remark utility. :) Currently there are is an outstanding performance issue (see the TODO) with the bitstream2yaml case. I decided that I'd keep the tool small to start with and have the yaml2bitstream and bitstream2yaml cases be symmetric. Also I moved the remarks documentation to its own header because it seems a little out of place with "basic commands" and "developer tools"; it's really kind of its own thing. Differential Revision: https://reviews.llvm.org/D133646
2022-09-09 19:58:02 -07:00
[llvm-remarkutil] Add an option to print out function sizes This adds an `instruction-count` command to llvm-remarkutil. ``` llvm-remarkutil instruction-count --parser=<bitstream|yaml> <file> ``` This will, for now, only print out asm-printer `InstructionCount` remarks. Frequently I need to find out things like "what are the top 10 largest functions" in a given project. This makes it so we can find that information quickly and easily from any format of remarks. I chose a CSV because I usually want to stick these into a spreadsheet, and the data is two-dimensional. In the future, we may want to change this to another format if we add more complicated data. Differential Revision: https://reviews.llvm.org/D134765
2022-09-27 14:26:37 -07:00
; YAMLPARSER: error: document root is not of mapping type.
Add a utility for converting between different types of remarks This adds llvm-remarkutil. This is intended to be a general tool for doing stuff with/to remark files. This patch gives it the following powers: * `bitstream2yaml` - To convert bitstream remarks to YAML * `yaml2bitstream` - To convert YAML remarks to bitstream remarks These are both implemented as subcommands, like `llvm-remarkutil bitstream2yaml <input_file> -o -` I ran into an issue where I had some bitstream remarks coming from CI, and I wanted to be able to do stuff with them (e.g. visualize them). But then I noticed we didn't have any tooling for doing that, so I decided to write this thing. Being able to output YAML as a start seemed like a good idea, since it would allow people to reuse any tooling they may have written based around YAML remarks. Hopefully it can grow into a more featureful remark utility. :) Currently there are is an outstanding performance issue (see the TODO) with the bitstream2yaml case. I decided that I'd keep the tool small to start with and have the yaml2bitstream and bitstream2yaml cases be symmetric. Also I moved the remarks documentation to its own header because it seems a little out of place with "basic commands" and "developer tools"; it's really kind of its own thing. Differential Revision: https://reviews.llvm.org/D133646
2022-09-09 19:58:02 -07:00
; An empty bitstream file is valid.
; BITSTREAM2YAML-NOT: error
[llvm-remarkutil] Add an option to print out function sizes This adds an `instruction-count` command to llvm-remarkutil. ``` llvm-remarkutil instruction-count --parser=<bitstream|yaml> <file> ``` This will, for now, only print out asm-printer `InstructionCount` remarks. Frequently I need to find out things like "what are the top 10 largest functions" in a given project. This makes it so we can find that information quickly and easily from any format of remarks. I chose a CSV because I usually want to stick these into a spreadsheet, and the data is two-dimensional. In the future, we may want to change this to another format if we add more complicated data. Differential Revision: https://reviews.llvm.org/D134765
2022-09-27 14:26:37 -07:00
; SIZEBITSTREAM-LABEL: Function,InstructionCount
Recommit "Add an option to print out annotation remark count." Add missing new line for `llvm/docs/CommandGuide/llvm-remarkutil.rst` This reverts commit 0f7fcb4c670fbef2c25b835fdfdd29598c6c13ae.
2023-04-07 23:42:39 +01:00
; SIZEBITSTREAM-EMPTY:
; ANNOTATIONBITSTREAM-LABEL: Function,Count
; ANNOTATIONBITSTREAM-EMPTY:
[Remarks] Introduce count subcommand for llvm-remarkutil. (#66214) This tool is a generic remark counter reporting count based on specified properties. The counter can be used to count remarks individually and filter them based on name, type and pass or count using remark arguments.
2023-10-12 16:03:39 +01:00
; COUNTBITSTREAM-LABEL: Source,Count
; COUNTBITSTREAM-EMPTY:
Reference in New Issue Copy Permalink