Limit perf data buffer during feature checking
authorIlya Leoshkevich <iii@linux.ibm.com>
Tue, 8 Dec 2020 12:17:58 +0000 (13:17 +0100)
committerIlya Leoshkevich <iii@linux.ibm.com>
Mon, 14 Dec 2020 11:59:04 +0000 (12:59 +0100)
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.

gcc/testsuite/lib/target-supports.exp

index 7e3cf29c1ce6793239a8f598bfa12acd51480db6..ad38b75659b48c8658af8c294c0f33015339afe1 100644 (file)
@@ -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