Displaying 3 results from an estimated 3 matches for "no_frame_point".
Did you mean:
no_frame_pointer
2012 Apr 30
0
[LLVMdev] [cfe-dev] [RFC] Encoding Compile Flags into the IR
...ng that we have a
magic bullet for passing semantic info from the FE to some passes.
* As you mention, this is probably the tip of the iceberg. Maybe we
should explore it a bit more with the tools we have before declaring
them insufficient. Duncan is working on fp precision, you can probably
add a no_frame_pointer metadata to functions and from there we will
have a better idea of how things are going.
Cheers,
Rafael
2012 Apr 30
2
[LLVMdev] [cfe-dev] [RFC] Encoding Compile Flags into the IR
...re about. The Module is the one which knows about the metadata.)
> * As you mention, this is probably the tip of the iceberg. Maybe we
> should explore it a bit more with the tools we have before declaring
> them insufficient. Duncan is working on fp precision, you can probably
> add a no_frame_pointer metadata to functions and from there we will
> have a better idea of how things are going.
>
I'd rather not start coding before we can agree on a concrete implementation.
-bw
2012 Apr 29
8
[LLVMdev] [RFC] Encoding Compile Flags into the IR
Hi,
Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of the proverbial iceberg.
Goals
=====
My goals for whichever solution we come up with are