Displaying 3 results from an estimated 3 matches for "973fb29f".
2013 May 13
2
[LLVMdev] [PATCH] 3.3 Release fix on ARM - atomics
...test, to make sure the behaviour
remains different (and documented).
I'm applying your patch to my tree now and will let you know.
cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130513/973fb29f/attachment.html>
2013 May 13
0
[LLVMdev] [PATCH] 3.3 Release fix on ARM - atomics
> I have asked on #gcc what gcc does. I have posted a detailed
> description in the bug, but the summary is that there is some
> cooperation with the kernel going on that should make it safe to set
> MaxAtomicInlineWidth to 64 when targeting linux armv6 or newer. Hard
> float using it then just becomes a consequence of it implying armv7.
>
> I know think we need something like
2013 May 13
5
[LLVMdev] [PATCH] 3.3 Release fix on ARM - atomics
On 13 May 2013 10:59, Renato Golin <renato.golin at linaro.org> wrote:
> Hi Rafael,
>
> As you mentioned in the bug, we should only apply this change when
> hard-float is set, which it is by default on armv7a, I presume.
>
> From that part of the code, I can infer that by the time
> "MaxAtomicPromoteWidth = 64;", the variable SoftFloat is not properly set,
>