ext/mbstring: move another test case that only works on 64 bits

Author: Girgias

ext/mbstring/tests/mb_decode_numericentity.phpt

@@ -106,9 +106,6 @@ test("Starting entity immediately after hex entity which is too long", "&#x11111
 test("Starting entity immediately after invalid decimal entity", "&#0A", "&#0A", [0x1, 0xFFFF, 0, 0xFFFF], 'ASCII');
 test("Starting entity immediately after invalid hex entity", "&#x0A", "&#x0A", [0x1, 0xFFFF, 0, 0xFFFF], 'ASCII');
 
-// Previously, signed arithmetic was used on convmap entries
-test("Regression test (convmap entries are now treated as unsigned)", "&#7,", "?,", [0x22FFFF11, 0xBF111189, 0x67726511, 0x1161E719], "ASCII");
-
 // Try with '&', '&#', or '&#' at the end of a buffer of wchars, with more input
 // still left to process in the next buffer
 // (mb_decode_numericentity splits its input into 'chunks' and processes it one
@@ -179,4 +176,3 @@ Starting entity immediately after decimal entity which is too long: string(18) "
 Starting entity immediately after hex entity which is too long: string(17) "&#x111111111A" => string(13) "&#x111111111A" (Good)
 Starting entity immediately after invalid decimal entity: string(8) "&#0A" => string(4) "&#0A" (Good)
 Starting entity immediately after invalid hex entity: string(9) "&#x0A" => string(5) "&#x0A" (Good)
-Regression test (convmap entries are now treated as unsigned): string(4) "&#7," => string(2) "?," (Good)

ext/mbstring/tests/mb_decode_numericentity_large_ints.phpt

@@ -49,10 +49,14 @@ test("Regression test (entity which decodes to 0xFFFFFFFF)", "", "?", [0xFF
 // because some text encodings did not properly invoke the next flush function in the chain
 test("Regression test (truncation of successive & with JIS encoding)", "&&&", "&&&", [0x20FF37FF, 0x7202F569, 0xC4090023, 0xF160], "JIS");
 
+// Previously, signed arithmetic was used on convmap entries
+test("Regression test (convmap entries are now treated as unsigned)", "&#7,", "?,", [0x22FFFF11, 0xBF111189, 0x67726511, 0x1161E719], "ASCII");
+
 ?>
 --EXPECT--
 Starting entity immediately after valid decimal entity which is just within maximum length: 000000260000002300000031000000300000003000000030000000300000003000000030000000300000003000000030000000260000002300000036000000350000003b => 3b9aca0000000041 (Good)
 Starting entity immediately after valid hex entity which is just within maximum length: 0000002600000023000000780000003100000031000000310000003100000031000000310000003100000031000000260000002300000036000000350000003b => 1111111100000041 (Good)
 Starting entity immediately after too-big decimal entity: string(17) "&#7001492542A" => string(13) "&#7001492542A" (Good)
 Regression test (entity which decodes to 0xFFFFFFFF): string(5) "" => string(1) "?" (Good)
 Regression test (truncation of successive & with JIS encoding): string(3) "&&&" => string(3) "&&&" (Good)
+Regression test (convmap entries are now treated as unsigned): string(4) "&#7," => string(2) "?," (Good)