Displaying 4 results from an estimated 4 matches for "handletargetfeatur".
Did you mean:
handletargetfeatures
2013 May 13
0
[LLVMdev] [PATCH] 3.3 Release fix on ARM - atomics
...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,
so a simple "if (!SoftFloat)" won't cut in there. It seems SoftFloat is
being set on HandleTargetFeatures() which is a virtual method, probably
called indirectly. Do you have a better place to set MaxAtomicInlineWidth =
64?
cheers,
--renato
On 13 May 2013 13:56, Renato Golin <renato.golin at linaro.org> wrote:
> Identified a while before the release, there is an issue with 64-bit
> at...
2013 May 13
2
[LLVMdev] [PATCH] 3.3 Release fix on ARM - atomics
Identified a while before the release, there is an issue with 64-bit
atomics on ARM that was making Clang mis-compile a lot of code, including
Clang itself.
http://llvm.org/bugs/show_bug.cgi?id=15429
Attached is a patch proposed by Benjamin with the corrections to the test.
I'm not an expert on how Clang lowers C11 atomics, but the resulting IR
seems correct, and after self-hosting Clang
2017 Aug 02
2
llvm-trunk errors with gcc-5.3.0 on SuSE Linux
...llvm::ARM::ArchKind)'
unsigned Extensions = llvm::ARM::getDefaultExtensions(CPU, Arch);
^
/export2/src/llvm-trunk/llvm/tools/clang/lib/Basic/Targets.cpp: In member
function 'virtual bool
{anonymous}::ARMTargetInfo::handleTargetFeatures(std::vector<std::__cxx11::basic_string<char>
>&, clang::DiagnosticsEngine&)':
/export2/src/llvm-trunk/llvm/tools/clang/lib/Basic/Targets.cpp:5588:26: error:
'PK_M' is not a member of 'llvm::ARM'
if (ArchProfile == llvm::ARM::PK_M)...
2013 May 13
5
[LLVMdev] [PATCH] 3.3 Release fix on ARM - atomics
...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,
> so a simple "if (!SoftFloat)" won't cut in there. It seems SoftFloat is
> being set on HandleTargetFeatures() which is a virtual method, probably
> called indirectly. Do you have a better place to set MaxAtomicInlineWidth =
> 64?
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 sho...