rust/tests/run-make/profile/Makefile

# needs-profiler-support
# ignore-cross-compile

include ../tools.mk

all:
	$(RUSTC) -g -Z profile test.rs
	$(call RUN,test) || exit 1
	[ -e "$(TMPDIR)/test.gcno" ] || (echo "No .gcno file"; exit 1)
	[ -e "$(TMPDIR)/test.gcda" ] || (echo "No .gcda file"; exit 1)
	$(RUSTC) -g -Z profile -Z profile-emit=$(TMPDIR)/abc/abc.gcda test.rs
	$(call RUN,test) || exit 1
	[ -e "$(TMPDIR)/abc/abc.gcda" ] || (echo "gcda file not emitted to defined path"; exit 1)
Use new `needs-(profiler\|sanitizer)-support` compiletest directive to clean up some run-make tests. 2019-04-18 08:49:41 -05:00			`# needs-profiler-support`
`ignore-cross-compile` remaining tests that run binaries 2023-08-30 06:45:57 -05:00			`# ignore-cross-compile`
Use new `needs-(profiler\|sanitizer)-support` compiletest directive to clean up some run-make tests. 2019-04-18 08:49:41 -05:00
Diagnose missing includes in run-make tests 2022-08-22 19:00:00 -05:00			`include ../tools.mk`
Add profiling support, through the rustc -Z profile flag. When -Z profile is passed, the GCDAProfiling LLVM pass is added to the pipeline, which uses debug information to instrument the IR. After compiling with -Z profile, the $(OUT_DIR)/$(CRATE_NAME).gcno file is created, containing initial profiling information. After running the program built, the $(OUT_DIR)/$(CRATE_NAME).gcda file is created, containing branch counters. The created .gcno and .gcda files can be processed using the "llvm-cov gcov" and "lcov" tools. The profiling data LLVM generates does not faithfully follow the GCC's format for .gcno and .gcda files, and so it will probably not work with other tools (such as gcov itself) that consume these files. 2017-02-13 03:57:50 -06:00
			`all:`
			`$(RUSTC) -g -Z profile test.rs`
			`$(call RUN,test) \|\| exit 1`
			`[ -e "$(TMPDIR)/test.gcno" ] \|\| (echo "No .gcno file"; exit 1)`
			`[ -e "$(TMPDIR)/test.gcda" ] \|\| (echo "No .gcda file"; exit 1)`
Add -Z profile-emit=<path> for Gcov gcda output. Adds a -Z flag to control the file path that the Gcov gcda output is written to during runtime. This flag expects a path and filename, e.g. -Z profile-emit=gcov/out/lib.gcda. This works similar to GCC/Clang's -fprofile-dir flag which allows control over the output path for gcda coverage files. 2020-05-26 12:41:40 -05:00			`$(RUSTC) -g -Z profile -Z profile-emit=$(TMPDIR)/abc/abc.gcda test.rs`
			`$(call RUN,test) \|\| exit 1`
			`[ -e "$(TMPDIR)/abc/abc.gcda" ] \|\| (echo "gcda file not emitted to defined path"; exit 1)`