From: Andrew Pinski <quic_apinski@quicinc.com>
Date: Sat, 7 Sep 2024 18:43:03 +0000 (-0700)
Subject: split-path: Fix dump wording about duplicating too many statements
X-Git-Tag: basepoints/gcc-16~6022
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=69d82c1dccb3583464228eb5449e29918eeb4ee4;p=thirdparty%2Fgcc.git

split-path: Fix dump wording about duplicating too many statements

It was pointed out in https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662183.html,
that the wording with this print has too many words.
Fixed thusly.

Pushed as obvious after a build and test for x86_64-linux-gnu.

gcc/ChangeLog:

	* gimple-ssa-split-paths.cc (is_feasible_trace): Fix wording
	on the print.

Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
---

diff --git a/gcc/gimple-ssa-split-paths.cc b/gcc/gimple-ssa-split-paths.cc
index 32b5c445760..886d85a94e4 100644
--- a/gcc/gimple-ssa-split-paths.cc
+++ b/gcc/gimple-ssa-split-paths.cc
@@ -208,7 +208,7 @@ is_feasible_trace (basic_block bb)
     {
       if (dump_file && (dump_flags & TDF_DETAILS))
 	fprintf (dump_file,
-		 "Duplicating block %d would be too duplicate "
+		 "Duplicating block %d would duplicate "
 		 "too many statments: %d >= %d\n",
 		 bb->index, num_stmts_in_join,
 		 param_max_jump_thread_duplication_stmts);