Displaying 3 results from an estimated 3 matches for "1b3fsfxw".
2008 Oct 22
9
[LLVMdev] Helping the optimizer along (__assume)
Hi,
I'm interested in whether or not there is a way of providing
source-level annotations to help LLVM with optimizations, similar to
VisualC++'s __assume facility
(http://msdn.microsoft.com/en-us/library/1b3fsfxw.aspx).
As part of our PHP compiler (phpcompiler.org), it would be great to be
able to annotate our generated C code with, for example, (var !=
NULL), or (var->type == STRING), and have that information passed
around (esp interprocedurally at link-time) by the LLVM optimizers. It
would also grea...
2008 Oct 22
0
[LLVMdev] Helping the optimizer along (__assume)
...PM, Paul Biggar <paul.biggar at gmail.com> wrote:
> Hi,
>
> I'm interested in whether or not there is a way of providing
> source-level annotations to help LLVM with optimizations, similar to
> VisualC++'s __assume facility
> (http://msdn.microsoft.com/en-us/library/1b3fsfxw.aspx).
No, nothing of the sort exists. There have been some rough
discussions of what would be involved, but there isn't really a plan
for how to implement it. It would probably end up being similar to
TBAA.
-Eli
2008 Oct 23
0
[LLVMdev] Helping the optimizer along (__assume)
...PM, Paul Biggar <paul.biggar at gmail.com> wrote:
> Hi,
>
> I'm interested in whether or not there is a way of providing
> source-level annotations to help LLVM with optimizations, similar to
> VisualC++'s __assume facility
> (http://msdn.microsoft.com/en-us/library/1b3fsfxw.aspx).
>
> As part of our PHP compiler (phpcompiler.org), it would be great to be
> able to annotate our generated C code with, for example, (var !=
> NULL), or (var->type == STRING), and have that information passed
> around (esp interprocedurally at link-time) by the LLVM optimi...