aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2024-09-05 11:06:12 +0200
committerJakub Jelinek <jakub@gcc.gnu.org>2024-09-05 11:06:12 +0200
commite9e4777ca2415a73e8db64a406c06a79add621e5 (patch)
tree10acd9f701aaa2f10b3c05938815237d7af07c64
parent3162abfb5098934e6ed9d4307a86a84d28823612 (diff)
downloadgcc-e9e4777ca2415a73e8db64a406c06a79add621e5.zip
gcc-e9e4777ca2415a73e8db64a406c06a79add621e5.tar.gz
gcc-e9e4777ca2415a73e8db64a406c06a79add621e5.tar.bz2
vrp: Fix up diagnostics wording
I've noticed non-standard wording of this diagnostics when looking at a miscompilation with --param=vrp-block-limit=0. Diagnostics generally shouldn't start with uppercase letter (unless the upper case would appear also in the middle of a sentence) and shouldn't be separate sentences with dot as separator, ; is IMHO more frequently used. 2024-09-05 Jakub Jelinek <jakub@redhat.com> * tree-vrp.cc (pass_vrp::execute): Start diagnostics with lowercase u rather than capital U, use semicolon instead of dot.
-rw-r--r--gcc/tree-vrp.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/tree-vrp.cc b/gcc/tree-vrp.cc
index e184e9a..23946c5 100644
--- a/gcc/tree-vrp.cc
+++ b/gcc/tree-vrp.cc
@@ -1337,7 +1337,7 @@ public:
{
use_fvrp = true;
warning (OPT_Wdisabled_optimization,
- "Using fast VRP algorithm. %d basic blocks"
+ "using fast VRP algorithm; %d basic blocks"
" exceeds %<--param=vrp-block-limit=%d%> limit",
n_basic_blocks_for_fn (fun),
param_vrp_block_limit);