[QST] [CuTeDSL] Compilation caused core dumped

What is your question?

Backtrace below. Any suggestions on how to figure out what's going?

(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140212788258368) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140212788258368) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140212788258368, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007f8b9b9eb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007f8b9b9d17f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x00007f8a3972d4df in ?? ()
   from /opt/conda/envs/cutlass/lib/python3.12/site-packages/nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_cutlass_ir.cpython-312-x86_64-linux-gnu.so
#6  0x00007f85d56f61f0 in ?? ()
#7  0x0000000000000008 in ?? ()
#8  0x00007f85d56f6290 in ?? ()
#9  0x00007f85d56f61f0 in ?? ()
#10 0x00007f85d56f63d0 in ?? ()
#11 0x01007f8a3f0c0574 in ?? ()
#12 0x00007f85d56f6120 in ?? ()
#13 0x00007f854ac80000 in ?? ()
#14 0x00007f854ac82ab0 in ?? ()
#15 0x00007f854b4c92b0 in ?? ()
#16 0x0000000000000001 in ?? ()
#17 0x00007f85d56f61f0 in ?? ()
#18 0x0000000000000010 in ?? ()
#19 0x00007f854aae3610 in ?? ()
#20 0x0000000000000001 in ?? ()
#21 0x00007f8a3f0c526c in ?? ()
   from /opt/conda/envs/cutlass/lib/python3.12/site-packages/nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_cutlass_ir.cpython-312-x86_64-linux-gnu.so
#22 0x00007f854a9f9001 in ?? ()
#23 0x00007f854a9f9070 in ?? ()
#24 0x00007f854ac80010 in ?? ()
#25 0x00007f854ac80060 in ?? ()
#26 0x00007f854ac80060 in ?? ()
#27 0x00007f854a5beae0 in ?? ()
#28 0x00007f85d56f6100 in ?? ()
#29 0x00007f854ac803f0 in ?? ()
#30 0x00007f854ac80490 in ?? ()
#31 0x00007f854ac80490 in ?? ()
#32 0x00007f85d56f61a8 in ?? ()
#33 0x00007f8a3f0c68cb in ?? ()
   from /opt/conda/envs/cutlass/lib/python3.12/site-packages/nvidia_cutlass_dsl/python_packages/cutlass/_mlir/_mlir_libs/_cutlass_ir.cpython-312-x86_64-linux-gnu.so
#34 0x00007f85d56f61b0 in ?? ()
#35 0x0000000400000001 in ?? ()
#36 0x00007f854ac74380 in ?? ()
#37 0x00007f8b9ba4d62b in _int_malloc (av=0x7f85d56f6950, bytes=140231745835680) at ./malloc/malloc.c:4307
#38 0x00007f854ac7f6c8 in ?? ()
#39 0x00007f854ac80ff0 in ?? ()
#40 0x00007f854ac81040 in ?? ()
#41 0x00007f854ac81040 in ?? ()
#42 0x0000000000000000 in ?? ()

Start by reproducing the CuTeDSL compilation failure and examining the GDB backtrace, especially the _cutlass_ir.cpython-312-x86_64-linux-gnu.so frames. The report needs a minimal compilation example and environment details before the abort can be localized; done should include identifying the cause and verifying a regression test or confirmed fix.