aboutsummaryrefslogtreecommitdiff
path: root/Makefile.in
diff options
context:
space:
mode:
authorEugene Rozenfeld <erozen@microsoft.com>2023-06-29 19:38:41 -0700
committerEugene Rozenfeld <erozen@microsoft.com>2023-07-07 13:06:28 -0700
commit275f7bc35fb864ef7867ff7e12bf5b27277ecc36 (patch)
tree2645f0ca270d4301567ca62e1e2612de64239722 /Makefile.in
parentbdf2737cda53a83332db1a1a021653447b05a7e7 (diff)
downloadgcc-275f7bc35fb864ef7867ff7e12bf5b27277ecc36.zip
gcc-275f7bc35fb864ef7867ff7e12bf5b27277ecc36.tar.gz
gcc-275f7bc35fb864ef7867ff7e12bf5b27277ecc36.tar.bz2
Collect both user and kernel events for autofdo tests and autoprofiledbootstrap
When we collect just user events for autofdo with lbr we get some events where branch sources are kernel addresses and branch targets are user addresses. Without kernel MMAP events create_gcov can't make sense of kernel addresses. Currently create_gcov fails if it can't map at least 95% of events. We sometimes get below this threshold with just user events. The change is to collect both user events and kernel events. Tested on x86_64-pc-linux-gnu. ChangeLog: * Makefile.in: Collect both kernel and user events for autofdo * Makefile.tpl: Collect both kernel and user events for autofdo gcc/testsuite/ChangeLog: * lib/target-supports.exp: Collect both kernel and user events for autofdo
Diffstat (limited to 'Makefile.in')
-rw-r--r--Makefile.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makefile.in b/Makefile.in
index f19a9db..04307ca 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -404,7 +404,7 @@ MAKEINFO = @MAKEINFO@
EXPECT = @EXPECT@
RUNTEST = @RUNTEST@
-AUTO_PROFILE = gcc-auto-profile -c 10000000
+AUTO_PROFILE = gcc-auto-profile --all -c 10000000
# This just becomes part of the MAKEINFO definition passed down to
# sub-makes. It lets flags be given on the command line while still