Legion Programming System

warning 232
Message: SOURCE REGION REQUIREMENT #1 OF COPY (ID #2) IN TASK #3 (ID #4) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 8360

back to message index

warning 233
Message: DESTINATION REGION REQUIREMENT #1 OF COPY (ID #2) IN TASK #3 (ID #4) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 6036
legion_ops.cc line 8375
legion_ops.cc line 8384
legion_ops.cc line 8467

back to message index

warning 245
Message: WARNING: mapper #1 faield to acquire instance for partition mapping operation in task #2 (ID #3) in 'map_partition' call. You may experience undefined behavior as a consequence.
legion_ops.cc line 5414
legion_ops.cc line 17248

back to message index

warning 1001
Message: Performing a blocking is_empty test on a in non-leaf task #1 (UID #2) is a violation of Legion's deferred execution model best practices. You may notice a severe performance degradation. Warning string: #3
runtime.cc line 1767

back to message index

warning 1002
Message: Waiting for all futures in a future map in non-leaf task #1 (UID #2) is a violation of Legion's deferred execution model best practices. You may notice a severe performance degredation. Warning string: #3
runtime.cc line 4350

back to message index

warning 1003
Message: Waiting for a physical region to be valid in non-leaf task #1 (UID #2) is a violation of Legion's deferred execution model best practices. You may notice a severe performance degradation. Warning string: #3
runtime.cc line 5307
runtime.cc line 5315

back to message index

warning 1004
Message: Request for 'get_piece_iterator' was performed on a physical region in task #1 (ID #2) without first waiting for the physical region to be valid. Legion is performing the wait for you. Warning string: #3
runtime.cc line 5326
runtime.cc line 5527
runtime.cc line 5571

back to message index

warning 1005
Message: Padding ccessor construction in non-leaf task #1 (UID #2) is a blocking operation in violation of Legion's deferred execution model best practices. You may notice a severe performance degradation. Warning string: #3
runtime.cc line 5689
runtime.cc line 5838

back to message index

warning 1006
Message: Accessor construction was performed on an unmapped region in task #1 (UID #2). Legion is mapping it for you. Please try to be more careful. Warning string: #3
runtime.cc line 5707

back to message index

warning 1007
Message: creating read-write accessor for field #1 in task #2 which only has WRITE_DISCARD privileges. You may be accessing uninitialized data. Warning string: #3
runtime.cc line 5629

back to message index

warning 1008
Message: NO PROCESSOR CONSTRAINT SPECIFIED FOR VARIANT #1 (ID #2) OF TASK #3 (ID #4)! ASSUMING LOC_PROC!
runtime.cc line 17889
runtime.cc line 18026

back to message index

warning 1009
Message: Projection functor #1 is being dynamically registered for a multi-node run with #2 nodes. It is currently the responsibility of the application to ensure that this projection functor is registered on all nodes where it will be required. Warning string: #3
runtime.cc line 23278

back to message index

warning 1010
Message: duplicate calls to configure_MPI_interoperability on rank #1
runtime.cc line 35308

back to message index

warning 1011
Message: THERE ARE NEW METHODS FOR PROJECTION FUNCTORS THAT MUST BE OVERRIDEN! CALLING DEPRECATED METHODS FOR NOW!
legion.cc line 3810
legion.cc line 3885

back to message index

warning 1012
Message: Ignoring request to create instance in memory
legion_instances.cc line 3835

back to message index

warning 1013
Message: Mapper #1 requested a profiling measurement of type #2 which is not applicable to operation #3 (UID #4) and will be ignored.
legion_ops.cc line 2015

back to message index

warning 1014
Message: REGION REQUIREMENT OF INLINE MAPPING IN TASK #1 (ID #2) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 4694

back to message index

warning 1015
Message: mapper #1 failed to acquires instances for region requirement #2 of task #3 (ID #4) in 'postmap_task' call. You may experience undefined behavior as a consequence.
legion_ops.cc line 8097
legion_tasks.cc line 3078
legion_tasks.cc line 4540

back to message index

warning 1016
Message: SOURCE REGION REQUIREMENT #1 OF COPY (ID #2) IN TASK #3 (ID #4) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 5969

back to message index

warning 1017
Message: DESTINATION REGION REQUIREMENT #1 OF COPY (ID #2) IN TASK #3 (ID #4) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 5984

back to message index

warning 1019
Message: Region requirements #1 and #2 of index copy #3 in parent task #4 (UID #5) are potentially interfering. It's possible that this is a false positive if there are projection region requirements and each of the point copies are non-interfering. If the runtime is built in debug mode then it will check that the region requirements of all points are actually non-interfering. If you see no further error messages for this index task launch then everything is good.
legion_ops.cc line 9096

back to message index

warning 1020
Message: PRIVILEGE FIELDS OF ACQUIRE OPERATIONIN TASK #1 (ID #2) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 12184

back to message index

warning 1021
Message: PRIVILEGE FIELDS OF RELEASE OPERATIONIN TASK #1 (ID #2) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_ops.cc line 12986

back to message index

warning 1022
Message: INDEX ATTACH OPERATION ISSUED WITH NO PRIVILEGE FIELDS IN TASK #1 (ID #2)! DID YOU FORGET TO SPECIFY THEM?!?
legion_ops.cc line 20081
legion_ops.cc line 20131
legion_ops.cc line 20731

back to message index

warning 1024
Message: REGION REQUIREMENT #1 OF TASK #2 (ID #3) HAS NO PRIVILEGE FIELDS! DID YOU FORGET THEM?!?
legion_tasks.cc line 686

back to message index

warning 1025
Message: Ignoring discard request with no fields in task #1 (UID #2)
legion_context.cc line 7397
legion_context.cc line 7441
legion_context.cc line 7497
legion_context.cc line 19106
legion_context.cc line 19185
legion_context.cc line 19258

back to message index

warning 1026
Message: Empty output target_procs from call to 'map_task' by mapper #1 for task #2 (ID #3). Adding the 'target_proc'
legion_tasks.cc line 2699

back to message index

warning 1027
Message: Ignoring spurious additional target processors requested in 'map_task' for task #1 (ID #2) by mapper #3 because task is part of a must epoch launch.
legion_tasks.cc line 2731

back to message index

warning 1028
Message: Ignoring processor request of
legion_tasks.cc line 2741

back to message index

warning 1030
Message: Mapper #1 requested a composite instance be created for region requirement #2 of task #3 (ID #4) for a post mapping. The request is being ignored.
legion_tasks.cc line 4550

back to message index

warning 1031
Message: Mapper #1 requested to inline task #2 (UID #3) but the 'enable_inlining' option was not set on the task launcher so the request is being ignored
legion_tasks.cc line 6704
legion_tasks.cc line 10172

back to message index

back to message index

warning 1047
Message: Waiting on a future in non-leaf task #1 (UID #2) is a violation of Legion's deferred execution model best practices. You may notice a severe performance degradation. Warning string: #3
runtime.cc line 1032

back to message index

back to message index

warning 1058
Message: Ignoring empty index task launch in task #1 (ID #2)
legion_context.cc line 7014
legion_context.cc line 7067
legion_context.cc line 18572

back to message index

warning 1071
Message: Region requirement #1 of operation #2 (UID #3) in parent task #4 (UID #5) is using uninitialized data for field(s) #6 of logical region (#7,#8,#9)
legion_ops.cc line 1894

back to message index

warning 1082
Message: Mapper #1 requested a profiling measurement of type #2 which is not applicable to task #3 (UID #4) and will be ignored.
legion_tasks.cc line 2850

back to message index

warning 1083
Message: Region tree state logging is disabled. To enable region tree state logging compile in debug mode.
runtime.cc line 34412

back to message index

warning 1085
Message: Ignoring empty index space fill in task #1 (ID #2)
legion_context.cc line 7449

back to message index

warning 1086
Message: Ignoring empty index space copy in task #1 (ID #2)
legion_context.cc line 7574

back to message index

warning 1087
Message: Variant #1 of task #2 (UID #3) was not marked as an 'inner' variant but it only launched operations and did not make any accessors. Did you forget the 'inner' annotation?
legion_context.cc line 12195
legion_context.cc line 12222

back to message index

warning 1088
Message: Mapper #1 requested post mapping instances be created for region requirement #2 of task #3 (ID #4), but this region requirement has REDUCE privileges. The request is being ignored.
legion_tasks.cc line 4469
legion_tasks.cc line 4480
legion_tasks.cc line 4491

back to message index

warning 1089
Message: Ignoring release request in unsupported mapper call #1 in mapper #2
legion_mapping.cc line 1746
legion_mapping.cc line 1763
legion_mapping.cc line 1781

back to message index

warning 1091
Message: Using a generic accessor for accessing a physical instance of task #1 (UID #2). Generic accessors are very slow and are strongly discouraged for use in high performance code. Warning string: #3
runtime.cc line 5726
runtime.cc line 5851

back to message index

warning 1092
Message: You should not specify -lg:prof_logfile when running with -lg:serializer ascii\n legion_prof output will be written to '-logfile ' instead
legion_profiling.cc line 2305

back to message index

warning 1093
Message: Mapper #1 requested change of priority for parent task #2 (UID #3) when launching child task #4 (UID #5), but the parent context does not support parent task priority mutation
legion_tasks.cc line 762

back to message index

warning 1095
Message: Ignoring request for mapper #1 to set garbage collection priority on an external instance
legion_mapping.cc line 1576

back to message index

warning 1096
Message: Ignoring invalid instance output from mapper #1 for select sources call on #2 (UID #3)
legion_ops.cc line 2854

back to message index

warning 1097
Message: WARNING: The runtime has failed to memoize the trace more than #1 times, due to the absence of a replayable template. It is highly likely that trace #2 in task #3 (UID #4) will not be memoized for the rest of execution. The most recent template was not replayable for the following reason: #5. Please change the mapper to stop making memoization requests.
legion_trace.cc line 2400

back to message index

warning 1098
Message: Internal runtime performance warning: equivalence set #1 has #2 different users which is the same as the sampling rate of #3. Region requirement #4 of operation #5 (UID #6) triggered this warning. Please report this application use case to the Legion developers mailing list.
legion_analysis.cc line 14224

back to message index

warning 1099
Message: Ignoring request by mapper #1 to not track valid instances for region requirement #2 of task #3 (UID #4) because region requirement does not have read-only privileges.
legion_ops.cc line 5431
legion_tasks.cc line 3253

back to message index

warning 1100
Message: Index space #1 was leaked out of task tree rooted by task #2
legion_context.cc line 6524
legion_context.cc line 6575
legion_context.cc line 6605
legion_context.cc line 6619
legion_context.cc line 6633

back to message index

warning 1101
Message: Duplicate deletions were performed for region (#1,#2,#3) in task tree rooted by #4
legion_context.cc line 6149
legion_context.cc line 6454
legion_context.cc line 6469
legion_context.cc line 6483
legion_context.cc line 6496
legion_context.cc line 6509
legion_context.cc line 18049

back to message index

warning 1102
Message: WARNING: The runtime has created #1 new replayable templates for trace #2 in task #3 (UID #4) without replaying any existing templates. This may mean that your mapper is not making mapper decisions conducive to replaying templates. Please check that your mapper is making decisions that align with prior templates. If you believe that this number of templates is reasonable please adjust the settings for LEGION_NEW_TEMPLATE_WARNING_COUNT in legion_config.h.
legion_trace.cc line 1900
legion_trace.cc line 2373

back to message index

warning 1103
Message: Custom serdez operator #1 was dynamically registered outside of a registration callback invocation. In the near future this will become an error in order to support task subprocesses. Please use 'perform_registration_callback' to generate a callback where it will be safe to perform dynamic registrations.
runtime.cc line 7801
runtime.cc line 7833
runtime.cc line 23270
runtime.cc line 23530
runtime.cc line 23782
runtime.cc line 35685
runtime.cc line 35705

back to message index

warning 1104
Message: Parent task #1 (UID #2) issued index space task #3 (UID #4) with non-scalable projection region requirement #5 that ensures all point tasks will be reading and writing to the same logical region. This implies there will be no task parallelism in this index space task launch.
legion_tasks.cc line 10108

back to message index

warning 1105
Message: Failed to inline task #1 (UID #2) into parent task #3 (UID #4) because there was no mapped region for region requirement #5 to use. Currently all regions must be mapped in the parent task in order to allow for inlining. If you believe you have a compelling use case for inline a task with virtually mapped regions then please contact the Legion developers.
legion_context.cc line 12509

back to message index

warning 1106
Message: WARNING: Sharding functor #1 is being dynamically registered for a multi-node run with #2 nodes. It is currently the responsibility of the application to ensure that this sharding functor is registered on all nodes where it will be required. Warning string: #3
runtime.cc line 23538

back to message index

warning 1108
Message: WARNING: futures returned from control replicated task #1 have different sizes of #2 and #3 bytes!
legion_replication.cc line 10828

back to message index

warning 1109
Message: Inlining is not currently supported for replicated tasks such as #1 (UID #2)
legion_context.cc line 18455
legion_context.cc line 18524
legion_context.cc line 18606

back to message index

warning 1110
Message: Ignoring equivalence sets reset in #1 (UID #2) because it contains no fields.
legion_context.cc line 6187
legion_context.cc line 6196
legion_context.cc line 18101
legion_context.cc line 18110

back to message index

warning 1111
Message: Control replicated task #1 (UID #2) had #3 mismatched unordered operations at the end of its execution that are now leaked.
legion_context.cc line 18376

back to message index

warning 1112
Message: Call to partitioning function #1 in #2 (UID #3) specified partition was #4 but the partition is complete. This could lead to a performance bug.
legion_context.cc line 5272
legion_context.cc line 5300

back to message index

warning 1113
Message: WARNING: #1 memory
legion_ops.cc line 20163
legion_ops.cc line 21419

back to message index

warning 1115
Message: WARNING: Performing copy-across reduction hammer with #1 instances into a single instance from collective manager #2 to normal manager #3. Please report this use case to the Legion developers' mailing list.
legion_views.cc line 1806

back to message index

warning 1116
Message: Ignoring request by mapper #1 to check for collective usage for region requirement #2 of task #3 (UID #4) because region requirement has writing privileges.
legion_tasks.cc line 788

back to message index

warning 1117
Message: Unsupported request to replicate task #1 (UID #2) during trace capture by mapper #3. Legion does not currently support replication of tasks inside of physical traces at the moment. You can request support for this feature by emailing the the Legion developers list or opening a github issue. The mapper call to replicate_task is being elided.
legion_tasks.cc line 844
legion_tasks.cc line 855
legion_tasks.cc line 875
legion_tasks.cc line 3799

back to message index

warning 1118
Message: Mapper #1 selected non-concurrent task variant #2 for task #3 (UID #4) which was launched as a concurrent index space task launch. Concurrent index space task launches have additional overhead associated with them so you should really only use them if you intend to use concurrent task variants. Also note this warning may turn into an error if any of the point tasks of this index task selected a concurrent variant.
legion_tasks.cc line 1527

back to message index

warning 1119
Message: Mapper #1 requested to replicate task #2 (UID #3) but only reqeuested one shard to be made. Since one shard does not actually constitute replication, Legion is ignoring this request and the task will be mapped like normal. If the mapper intended to not perform replication it should return an empty vector of target processors for 'replicate_task'.
legion_tasks.cc line 3823

back to message index

warning 1120
Message: WARNING! Leaf task #1 (UID #2) attempted to allocate a DeferredBuffer/Value/Reduction of #3 bytes in #4 memory but no space was reserved for dynamic allocations during the lifetime of this task. Legion has managed to procure for you an allocation this time but there is no guarantee that you will be so lucky the next time. We strongly encourage all users to place tight upper bounds on the required memory for all leaf tasks either statically at the point of task variant registration or dynamically at the point that the task is mapped.
legion_context.cc line 25720
legion_context.cc line 25883

back to message index

warning 1121
Message: Mapper #1 requested an unbound memory pool in #2 memory for leaf task #3 (UID #4). Unbound memory pools are very bad for performance and we strongly encourage all users to avoid using them except for extenuating circumstances when the amount of dynamic memory required by a task is truly unbounded.
legion_tasks.cc line 4726
legion_tasks.cc line 4797
legion_tasks.cc line 4945

back to message index

warning 1122
Message: Detected unbounded pool in trace. Mapper #1 requested to trace task #2 (UID #3) with an unbounded memory pool in #4 memory. Unbounded pools are not permitted in traces and will prevent this recording of the trace from being replayed.
legion_tasks.cc line 3764

back to message index

warning 1123
Message: WARNING: Concurrent coloring functor #1 is being dynamically registered for a multi-node run with #2 nodes. It is currently the responsibility of the application to ensure that this concurrent coloring functor is registered on all nodes where it will be required. Warning string: #3
runtime.cc line 23790

back to message index