Displaying 3 results from an estimated 3 matches for "__builtin_foo".
Did you mean:
__builtin_ffs
2013 May 20
1
[LLVMdev] _Znwm is not a builtin
...quot;hasFnAttr(Attribute::NoBuiltin)" abort though: it will be a common bug to call this instead of your new accessor.
> This (incidentally) also exactly matches what we want for another Clang feature: we want a -fno-builtin-foo which makes 'foo' not be a builtin (but we still want __builtin_foo to have the builtin behavior). This, again, is not possible with the existing 'nobuiltin' attribute, due to the function pointer problem. Instead, Clang currently just provides -fno-builtin, and even *that* only provides a broken half-implementation -- it calls TargetLibraryInfo::disableAll...
2013 May 16
0
[LLVMdev] _Znwm is not a builtin
...attribute. The 'builtin' attribute
has the effect of canceling out the 'nobuiltin' attribute on the
declaration.
This (incidentally) also exactly matches what we want for another Clang
feature: we want a -fno-builtin-foo which makes 'foo' not be a builtin (but
we still want __builtin_foo to have the builtin behavior). This, again, is
not possible with the existing 'nobuiltin' attribute, due to the function
pointer problem. Instead, Clang currently just provides -fno-builtin, and
even *that* only provides a broken half-implementation -- it calls
TargetLibraryInfo::disableAll...
2013 May 16
2
[LLVMdev] _Znwm is not a builtin
On May 15, 2013, at 10:32 PM, Richard Smith <richard at metafoo.co.uk> wrote:
>>> Initially, I'm just concerned about keeping the optimizations we already perform, such as globalopt lowering a new/delete pair into a global, while disabling the non-conforming variations of those optimizations. But we're also permitted to merge multiple allocations into one if they have