[v2] LoongArch:Change the default value of LARCH_CALL_RATIO to 6 on the LoongArch architecture.

Message ID 20230607074909.3541-1-chenxl04200420@163.com
State Accepted
Headers
Series [v2] LoongArch:Change the default value of LARCH_CALL_RATIO to 6 on the LoongArch architecture. |

Checks

Context Check Description
snail/gcc-patch-check success Github commit url

Commit Message

chen xiaolong June 7, 2023, 7:49 a.m. UTC
  During the regression testing of the LoongArch architecture GCC, it was
found that the tests in the pr90883.C file failed. The problem was modulated and
found that the error was caused by setting the macro LARCH_CALL_RATIO to a too
large value. Combined with the actual LoongArch architecture, the different
thresholds for meeting the test conditions were tested using the engineering method
(SPEC CPU 2006), and the results showed that its optimal threshold should be set
to 6.
gcc/ChangeLog:

	* config/loongarch/loongarch.h (LARCH_CALL_RATIO):
	Modify the value of macro LARCH_CALL_RATIO on LoongArch to make it
        perform optimally.
---
 gcc/config/loongarch/loongarch.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
  

Patch

diff --git a/gcc/config/loongarch/loongarch.h b/gcc/config/loongarch/loongarch.h
index f8167875646..adea7333925 100644
--- a/gcc/config/loongarch/loongarch.h
+++ b/gcc/config/loongarch/loongarch.h
@@ -1055,7 +1055,7 @@  typedef struct {
 /* The base cost of a memcpy call, for MOVE_RATIO and friends.  These
    values were determined experimentally by benchmarking with CSiBE.
 */
-#define LARCH_CALL_RATIO 8
+#define LARCH_CALL_RATIO 6
 
 /* Any loop-based implementation of cpymemsi will have at least
    LARCH_MAX_MOVE_BYTES_STRAIGHT / UNITS_PER_WORD memory-to-memory