https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985
--- Comment #17 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Martin Jambor from comment #16)
> I'll have look, hopefully on Monday.
Thanks Martin.
To reproduce the problem:
1. Revert this patch:
commit d7bb8eaade3cd3aa70715c8567b4d7b08098e699 (master, clean)
Author: Aldy Hernandez <al...@redhat.com>
Date: Fri May 10 00:29:13 2024 +0200
Revert: "Enable prange support." [PR114985]
2. Trap on pointer mismatches:
diff --git a/gcc/range-op.cc b/gcc/range-op.cc
index 000ec802e66..c14b72c19de 100644
--- a/gcc/range-op.cc
+++ b/gcc/range-op.cc
@@ -52,7 +52,7 @@ along with GCC; see the file COPYING3. If not see
// Set to 1 to trap on range-op entries that cannot handle the pointer
// combination being requested. This is a temporary sanity check to
// aid in debugging, and will be removed later in the release cycle.
-#define TRAP_ON_UNHANDLED_POINTER_OPERATORS 0
+#define TRAP_ON_UNHANDLED_POINTER_OPERATORS 1
// Instantiate the operators which apply to multiple types here.
I will also attach a preprocessed file to reproduce the problem on ppc64le that
can save you some time.
