Displaying 3 results from an estimated 3 matches for "__builtin___clear_cache".
2014 Mar 14
2
[LLVMdev] __builtin___clear_cache
...his bug:
http://llvm.org/bugs/show_bug.cgi?id=19142
I need an LLVM intrinsic to communicate the need to lower the builtin
wither to noop or a call or even a sequence of instructions. I thought
about:
void @llvm.clear_cache(i8 * begin, i8 * end)
to simulate precisely GCC's builtin:
void __builtin___clear_cache (char *begin, char *end)
which will be, by default, nothing. On ARM and MIPS, it'll call __clear_cache.
Is that a good plan?
cheers,
--renato
2014 Mar 14
2
[LLVMdev] __builtin___clear_cache
On 14 March 2014 16:34, JF Bastien <jfb at google.com> wrote:
> How does this overlap with:
>
> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140310/thread.html#208333
The builtin was created to call __clear_cache() on platforms that need
it (like ARM and MIPS), but to be ignored on others (like x86_64).
This builtin should call __clear_cache() from whatever
2014 Mar 28
2
[LLVMdev] Named Register Implementation
On 28 March 2014 16:12, Krzysztof Parzyszek <kparzysz at codeaurora.org> wrote:
> I mean how do you make sure that the "write" builtin does not look like dead
> code, and at the same time it's not treated as something that "changes
> everything".
On the IR level, I expect a call to an intrinsic to never be pruned.
But I also need more guarantees regarding