From 6bc8e5ba0c935dbe8a19065502771593f234ec0f Mon Sep 17 00:00:00 2001
From: Brad Chamberlain <bradcray@users.noreply.github.com>
Date: Wed, 29 Oct 2025 11:41:03 -0700
Subject: [PATCH] Inline the non-param nudge upper/lower bound routines

While looking at some generated code that used lo..<hi ranges today, I
was surprised to find a function call to compute the "hi-1" implied by
"hi", which seems like overkill in the generated C code.  This changes
the non-param versions of the routine to be inlined which seems like
it can only help, and likely not hurt, the compiler back-end.

---
Signed-off-by: Brad Chamberlain <bradcray@users.noreply.github.com>
---
 modules/internal/ChapelRange.chpl | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/internal/ChapelRange.chpl b/modules/internal/ChapelRange.chpl
index c55257a2ae32..d932a8e25812 100644
--- a/modules/internal/ChapelRange.chpl
+++ b/modules/internal/ChapelRange.chpl
@@ -432,13 +432,13 @@ module ChapelRange {
       compilerError("Ranges defined using bounds of type '" + low.type:string + ".." + high.type:string + "' are not currently supported");
   }
 
-  proc chpl__nudgeLowBound(low) {
+  inline proc chpl__nudgeLowBound(low) {
     return chpl__intToIdx(low.type, chpl__idxToInt(low) + 1);
   }
   proc chpl__nudgeLowBound(param low) param {
     return chpl__intToIdx(low.type, chpl__idxToInt(low) + 1);
   }
-  proc chpl__nudgeHighBound(high) {
+  inline proc chpl__nudgeHighBound(high) {
     return chpl__intToIdx(high.type, chpl__idxToInt(high) - 1);
   }
   proc chpl__nudgeHighBound(param high) param {