[LLVMdev] Proposal : Function Notes

[Evan Cheng]

On Aug 22, 2008, at 4:40 PM, Devang Patel wrote:

I like it. It's simple enough to understand. We can implement the easy  
(and most frequently used) stuff first and go from there.

>
>
> // 
> = 
> = 
> = 
> ----------------------------------------------------------------------= 
> ==//
> // Implementation Overview
> //
>
> [0] Implement llvm::Function Note store and access interface.
> [1] Update LLVM Asm Parser to recognize Function Notes.
> [2] Update LLVM Printer to print Function Notes.
> [3] Update LLVM BitCode Reader and Writer to handle Function Notes.
> [4] Update optimization passes to recognize "opt-size" property
>     Update the inliner to recognize "noinline" and "always_inline"  
> Notes.

Some naming inconsistency here. opt-size vs. always_inline. If there  
isn't a win to use the same name as gcc attribute, always-inline might  
be better.

> [5] Many code generation choices are encoded as global variables in
>     TargetOptions.h. Update code generation passes to read these  
> choices from
>     function notes and eliminate these global variables.
> [6] Update LTO to merge function Notes from various IR files  
> appropriately.

One issue I can think of. Options change. Their names can change, some  
can go away, etc. Do we have AutoUpgrade to upgrade them? Is there a  
better solution?

Evan


>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080825/1cafb7fc/attachment.html>