diff options
| author | Ilya Leoshkevich <iii@linux.ibm.com> | 2020-12-08 13:17:58 +0100 |
|---|---|---|
| committer | Ilya Leoshkevich <iii@linux.ibm.com> | 2020-12-14 12:59:04 +0100 |
| commit | 470a25b638fedcaa37ce0c4101f11b87e1fa7d79 (patch) | |
| tree | ef66fea3973ccc90bc6356bf6c83f059f10589a1 | |
| parent | f60c1b3102791b98de7c1ce951bce335394682ca (diff) | |
| download | gcc-470a25b638fedcaa37ce0c4101f11b87e1fa7d79.zip gcc-470a25b638fedcaa37ce0c4101f11b87e1fa7d79.tar.gz gcc-470a25b638fedcaa37ce0c4101f11b87e1fa7d79.tar.bz2 | |
Limit perf data buffer during feature checking
Commit 2ead1ab91123 ("Limit perf data buffer during profiling") added
-m8 to perf invocations during running tests, but the same problem
exists for checking whether perf is working in the first place.
gcc/testsuite/ChangeLog:
2020-12-08 Ilya Leoshkevich <iii@linux.ibm.com>
* lib/target-supports.exp(check_profiling_available): Limit
perf data buffer.
| -rw-r--r-- | gcc/testsuite/lib/target-supports.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 7e3cf29..ad38b75 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -654,7 +654,7 @@ proc check_profiling_available { test_what } { return 0 } global srcdir - set status [remote_exec host "$srcdir/../config/i386/gcc-auto-profile" "true -v >/dev/null"] + set status [remote_exec host "$srcdir/../config/i386/gcc-auto-profile" "-m8 true -v >/dev/null"] if { [lindex $status 0] != 0 } { verbose "autofdo not supported because perf does not work" return 0 |