xtensa: mmu: no need to ignore array bound for SoC MMU ranges

The #pragma to ignore array bounds for xtensa_soc_mmu_ranges[]
was a remnant before code refactoring during review. Since
this array is no longer declared __weak and as a zero length
array, the #pragma to ignore array bounds is no longer needed.
So remove them.

Signed-off-by: Daniel Leung <[email protected]>

arch/xtensa/core/ptables.c

@@ -284,19 +284,6 @@ static void xtensa_init_page_tables(void)
 		map_memory(range->start, range->end, attrs, shared);
 	}
 
-/**
- * GCC complains about usage of the SoC MMU range ARRAY_SIZE
- * (xtensa_soc_mmu_ranges) as the default weak declaration is
- * an empty array, and any access to its element is considered
- * out of bound access. However, we have a number of element
- * variable to guard against this (... if done correctly).
- * Besides, this will almost be overridden by the SoC layer.
- * So tell GCC to ignore this.
- */
-#if defined(__GNUC__)
-#pragma GCC diagnostic push
-#pragma GCC diagnostic ignored "-Warray-bounds"
-#endif
 	for (entry = 0; entry < xtensa_soc_mmu_ranges_num; entry++) {
 		const struct xtensa_mmu_range *range = &xtensa_soc_mmu_ranges[entry];
 		bool shared;
@@ -307,9 +294,7 @@ static void xtensa_init_page_tables(void)
 
 		map_memory(range->start, range->end, attrs, shared);
 	}
-#if defined(__GNUC__)
-#pragma GCC diagnostic pop
-#endif
+
 	/* Finally, the direct-mapped pages used in the page tables
 	 * must be fixed up to use the same cache attribute (but these
 	 * must be writable, obviously).  They shouldn't be left at