[LLVMdev] [DragonEgg] Mysterious FRAME coming from gimple to LLVM (original) (raw)

Dmitry N. Mikushin maemarcus at gmail.com
Tue Jul 31 07:04:38 PDT 2012

Hi Anton,

Still there, even with opts. I consulted with GCC guys and debugged f951 a little bit. The conclusion is that unfortunately this logic is always effective for nested calls using parent's data (through the GCC function called convert_nonlocal_reference_op). Consider the provided test case: it has one func embedded into another one, and data of parent is used in nested without being passed in arguments. In this case as I understand FRAME is always created. Still, our question is if it is good to keep it for LLVM. This thing introduces additional unexpected load/stores and phi-nodes.

2012/7/31 Anton Korobeynikov <anton at korobeynikov.info>

> According to comment in tree-nested.c, these frames should be only > introduced in case of debug or OpenMP lowering: in case of debug. What if you pass -O1 / -O2 / -Owhatever ?

-- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120731/72e4b57c/attachment.html>

More information about the llvm-dev mailing list