Legion Programming System

back to message index

fatal 2007
Message: unknown field ID #1 requested during instance creation
region_tree.cc line 13923
region_tree.cc line 13953

back to message index

fatal 2009
Message: Legion currently supports only the SOA layout for output regions, but output region #1 of task #2 (UID: #3) is mapped to a non-SOA layout. Please update the mapper to use SOA layout for all output regions.
legion_context.cc line 5672
legion_context.cc line 5799
legion_context.cc line 17234
legion_context.cc line 17364
legion_context.cc line 17538
legion_context.cc line 17644
legion_replication.cc line 12482
legion_tasks.cc line 3323
runtime.cc line 6442
runtime.cc line 6453
runtime.cc line 14249
runtime.cc line 14415

back to message index

fatal 2011
Message: Dynamic Custom Serdez IDs exceeded library ID offset #1
runtime.cc line 22492
runtime.cc line 22855
runtime.cc line 23120
runtime.cc line 23375
runtime.cc line 23629
runtime.cc line 24120
runtime.cc line 24353
runtime.cc line 24479

back to message index

fatal 2012
Message: Dynamic registration callbacks cannot be registered after the runtime has been started with multiple runtime instances.
runtime.cc line 35006
runtime.cc line 35011
runtime.cc line 35025
runtime.cc line 35522
runtime.cc line 35553

back to message index

fatal 2013
Message: Unsupported size #1 for consensus match in #2 (UID #3)
legion_context.cc line 13061

back to message index

fatal 2014
Message: Global registration callback function pointer #1 is not portable. All registration callbacks requesting to be performed 'globally' must be able to be recognized by a call to 'dladdr'. This requires that they come from a shared object or the binary is linked with the '-rdynamic' flag.
runtime.cc line 21197

back to message index

fatal 2015
Message: Unsafe re-use of reduction instance detected due to alternating un-flushed reduction operations #1 and #2. Please report this use case to the Legion developer's mailing list so that we can help you address it.
legion_analysis.cc line 16654
legion_analysis.cc line 16742

back to message index

fatal 2017
Message: Found an internal garbage collection race. Please run with -lg:safe_mapper and see if it reports any errors. If not, then please report this as a bug.
legion_context.cc line 6945
legion_instances.cc line 1712
legion_instances.cc line 1719

back to message index

fatal 2018
Message: Something requested a very strange pattern for collective instance rendezvous with different points asking to rendezvous with different field sets on the same physical instance. This isn't currently supported. Please report your use case to the Legion developer's mailing list.
legion_ops.cc line 3258

back to message index

fatal 2020
Message: Task #1 (UID #2) requested the creation of a dynamic collective while profiling for critical paths without recording all critical barrier arrivals. Critical path analysis with dynamic collectives requires that you use the '-lg:prof_all_critical_arrivals' flag.
legion_context.cc line 10547

back to message index

fatal 2021
Message: Legion does not currently suppport creating handshake with a value for 'legion_participants' different than '1'.
legion.cc line 7413
legion.cc line 7417
legion.cc line 7432
legion.cc line 7436

back to message index

fatal 2022
Message: Encountered a non-permissive unbouned memory pool in memory #1 while invoking #2 in mapper call #3 by mapper #4 while holding the concurrent mapper lock. This situation can and most likely will lead to a deadlock as mapper calls needed to ensure forward progress will not be able to run while this mapper is holding the lock and waiting for the unbounded pool allocation to finish. To work around this currently, concurrent mappers need to ensure that they are not holding the concurrent mapper lock while attempting to allocated in a memory containing non-permissive unbounded pools.
mapper_manager.cc line 1302
mapper_manager.cc line 1315
mapper_manager.cc line 1555

back to message index