search for: diagnosticinfostacksize

...n corresponding to a Function, in order to > issue a warning if the stack size is too large. > However I don't see a way to access this information from my host C++ > program. You can retrieve those warnings from your host program; if you call LLVMContext::setDiagnosticHandler, the DiagnosticInfoStackSize gets passed to your code instead of getting dumped to stderr. > > One approach I have investigated is writing a MachineFunctionPass that > could access the MachineFunctions and hence the stack size. However I > have not been able to get my MachineFunctionPass to run > without hit...

Hi all, I'm trying to get the amount of stack memory used by the functions I am JIT compiling with LLVM. I have a host C++ program, and I want to be able to access the stack size from the host C++ program. I see in PrologEpilogInserter.cpp that the computed stack size is read from the MachineFunction corresponding to a Function, in order to issue a warning if the stack size is too large.

.... Like Chandler said it could just be due to lack of stack sharing compared to GCC. There's a lot going on between the time when we generate IR from AST to the time this final machine pass is run. GCC might just be optimizing differently. On the other hand it could indeed be that LLVM's DiagnosticInfoStackSize is giving us a different value or computation than GCC's -Wframe-larger-than. It's worth double checking that we're using a similar function frame size computation here. Let's not write off either possibility given that the LLVM value wasn't originally intended for GCC comp...