Skip to content

Commit

Permalink
Remove reference to LoopVectorization
Browse files Browse the repository at this point in the history
[skip-ci]
  • Loading branch information
Zentrik committed Apr 21, 2024
1 parent 2ad4526 commit fdc3a98
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 7 deletions.
2 changes: 1 addition & 1 deletion contrib/bolt/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ FILES_TO_OPTIMIZE := $(shell for file in $(SYMLINKS_TO_OPTIMIZE); do readlink $(

AFTER_INSTRUMENT_MESSAGE:='Run `make finish_stage1` to finish off the build. $\
You can now optionally collect more profiling data by running Julia with an appropriate workload, $\
if you wish run `make clean_profiles` before to remove any profiling data generated by `make finish_stage1`. $\
if you wish, run `make clean_profiles` before doing so to remove any profiling data generated by `make finish_stage1`. $\
You should end up with some data in $(PROFILE_DIR). Afterwards run `make merge_data && make bolt`. $\

$(STAGE0_BUILD) $(STAGE1_BUILD):
Expand Down
11 changes: 5 additions & 6 deletions contrib/pgo-lto-bolt/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -61,19 +61,18 @@ FILES_TO_OPTIMIZE := $(shell for file in $(SYMLINKS_TO_OPTIMIZE); do readlink $(

AFTER_INSTRUMENT_MESSAGE:='Run `make finish_stage2` to finish off the build. $\
You can now optionally collect more profiling data by running Julia with an appropriate workload, $\
if you wish run `make clean_profiles` before to remove any profiling data generated by `make finish_stage2`. $\
if you wish, run `make clean_profiles` before doing so to remove any profiling data generated by `make finish_stage2`. $\
You should end up with some data in $(BOLT_PROFILE_DIR). Afterwards run `make merge_data && make bolt`. $\

# When building a single libLLVM.so we need to increase -vp-counters-per-site
# significantly
COUNTERS_PER_SITE:=6
# Note: profile counters are not atomic by default, https://discourse.llvm.org/t/profile-guided-optimization-pgo-related-questions-and-suggestions/75232/5

AFTER_STAGE1_MESSAGE:='Run `make clean-profiles` to start with a clean slate. $\
Then run Julia to collect realistic profile data, for example: `$(STAGE1_BUILD)/julia -O3 -e $\
'\''using Pkg; Pkg.add("LoopVectorization"); Pkg.test("LoopVectorization")'\''`. This $\
should produce about 15MB of data in $(PGO_PROFILE_DIR). Note that running extensive $\
scripts may result in counter overflows, which can be detected by running $\
AFTER_STAGE1_MESSAGE:='You can now optionally collect more profiling data for use in PGO by running Julia $\
with an appropriate workload. If you wish, run `make clean_profiles` before doing so to remove any profiling data $\
generated by building Julia. You should end up with about 15MB of data in $(PGO_PROFILE_DIR). $\
Note that running extensive scripts may result in counter overflows, which can be detected by running $\
`make top`. Afterwards run `make stage2`.'

TOOLCHAIN_FLAGS = $\
Expand Down

0 comments on commit fdc3a98

Please sign in to comment.