Displaying 4 results from an estimated 4 matches for "placeafter".
2012 Feb 13
3
[LLVMdev] LLVM GHC Backend: Tables Next To Code
...to specify a that a global variable should
appear before the corresponding function in the object code.
An example of a possible implementation of (2) has been recently
suggested by Gabor Greif. He proposes adding a "placebefore"
attribute to global variables (or, similarly, a "placeafter" attribute
for functions). The corresponding example is:
@foo_D = common global %struct.Descr zeroinitializer, align 8,
placebefore @foo
define i32 @foo() nounwind uwtable readnone {
ret i32 undef
}
The questions is whether the LLVM developers are willing to accept
such modifica...
2012 Feb 14
0
[LLVMdev] LLVM GHC Backend: Tables Next To Code
...the code" as two different LLVM values (a global value and a function) would mean that the optimizer will be tempted to put them into different sections, do dead code elimination, etc.
> He proposes adding a "placebefore"
> attribute to global variables (or, similarly, a "placeafter" attribute
> for functions). The corresponding example is:
This is a non-starter for a few reasons, but that doesn't mean that there aren't other reasonable options. I'd really like to see the codegen that you guys are after to try to help come up with another suggestion that...
2012 Mar 13
3
[LLVMdev] LLVM GHC Backend: Tables Next To Code
...t; as two different LLVM values (a global value and a function) would mean that the optimizer will be tempted to put them into different sections, do dead code elimination, etc.
>
>> He proposes adding a "placebefore"
>> attribute to global variables (or, similarly, a "placeafter" attribute
>> for functions). The corresponding example is:
>
> This is a non-starter for a few reasons, but that doesn't mean that there aren't other reasonable options. I'd really like to see the codegen that you guys are after to try to help come up with another su...
2012 Feb 14
3
[LLVMdev] LLVM GHC Backend: Tables Next To Code
...t; as two different LLVM values (a global value and a function) would mean that the optimizer will be tempted to put them into different sections, do dead code elimination, etc.
>
>> He proposes adding a "placebefore"
>> attribute to global variables (or, similarly, a "placeafter" attribute
>> for functions). The corresponding example is:
>
> This is a non-starter for a few reasons, but that doesn't mean that there aren't other reasonable options. I'd really like to see the codegen that you guys are after to try to help come up with another su...