blog:2020:0425_jit_compiler_part5_improvements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
blog:2020:0425_jit_compiler_part5_improvements [2020/07/10 12:11] – external edit 127.0.0.1blog:2020:0425_jit_compiler_part5_improvements [2022/11/18 09:28] (current) – external edit 127.0.0.1
Line 604: Line 604:
 } }
 </sxh> </sxh>
-  - Even when using LLVM 10.0.0, I would still get my segmentation fault when using this utility... It took me quite a long time to figure out what was happening but I finally realize this was because **somehow, the code I'm generating in my JIT compiler is not registering a destructor with the "%%__cxa_atexit%%" handler, but instead, with the legacy/obsolete "atexit" handler**. Unfortunately, I have no real idea why (yet).+  - Even when using LLVM 10.0.0, I would still get my segmentation fault when using this utility... It took me quite a long time to figure out what was happening but I finally realize this was because **somehow, the code I'm generating in my JIT compiler is not registering a destructor with the ** "%%__cxa_atexit%%" **handler, but instead, with the legacy/obsolete "atexit" handler** /*__*/ . Unfortunately, I have no real idea why (yet).
      
 <note>I've tried various setups with the command line arguments "-fno-use-cxa-atexit", "-fuse-cxa-atexit", "-fregister-global-dtors-with-atexit", but none of these really helped to use the cxa_atexit handler. But as a remainder, don't forget that I'm on windows 10 platform and using all the ms compatibility flags for Visual Studio... maybe that could be part of the explanation [Or maybe I just need to try harder...]</note> <note>I've tried various setups with the command line arguments "-fno-use-cxa-atexit", "-fuse-cxa-atexit", "-fregister-global-dtors-with-atexit", but none of these really helped to use the cxa_atexit handler. But as a remainder, don't forget that I'm on windows 10 platform and using all the ms compatibility flags for Visual Studio... maybe that could be part of the explanation [Or maybe I just need to try harder...]</note>
Line 1530: Line 1530:
  
  
-~~DISCUSSION~~+~~DISCUSSION:off~~
  
  
  • blog/2020/0425_jit_compiler_part5_improvements.1594383109.txt.gz
  • Last modified: 2020/07/10 12:11
  • by 127.0.0.1