Better position for error when wrong number of ports are returned by portNames

Author: krame505

src/Libraries/Base1/Prelude.bs

@@ -4590,7 +4590,8 @@ checkPortNames proxy base =
   let pn = portNames proxy base
   in
     if listLength pn /= valueOf n
-    then error $ "SplitPorts: " +++ base +++ " has " +++ integerToString (valueOf n) +++
+    then primError (getEvalPosition proxy) $
+      "SplitPorts: " +++ base +++ " has " +++ integerToString (valueOf n) +++
       " ports, but " +++ integerToString (listLength pn) +++ " port names were given"
     else pn
 

testsuite/bsc.verilog/splitports/BadSplitInst_TooManyPortNames.bs.bsc-vcomp-out.expected

@@ -1,7 +1,7 @@
 checking package dependencies
 compiling BadSplitInst_TooManyPortNames.bs
 code generation for sysBadSplitInst_TooManyPortNames starts
-Error: "Prelude.bs", line 4593, column 61: (S0015)
+Error: "BadSplitInst_TooManyPortNames.bs", line 17, column 12: (S0015)
   Bluespec evaluation-time error: SplitPorts: fooIn_1 has 2 ports, but 3 port
   names were given
   During elaboration of `sysBadSplitInst_TooManyPortNames' at