Displaying 4 results from an estimated 4 matches for "computellvmtriple".
2012 Jul 24
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
...t; work? That could be a pretty big deal, though it'd mostly be political and testing work. The actual implementation details are likely to not be that bad.
Making Thumb2 the default for any ARMv7 triple, on the other hand, is a change that could be made in a matter of minutes.
See ToolChain::ComputeLLVMTriple(). In particular, the following:
// Thumb2 is the default for V7 on Darwin.
//
// FIXME: Thumb should just be another -target-feaure, not in the triple.
StringRef Suffix =...
2016 Jun 24
7
Representing MIPS ABI information in the triple as ARM/X86 do for EABI/EABIHF/X32
...pectively to transform the triple for the backend.
In summary, human end users of tools such as clang will continue using the same triples as they always have. These tools will then resolve them down to the effective triple (for example, in functions like clang's ComputeEffectiveClangTriple(), ComputeLLVMTriple(), and computeTargetTriple()). The MIPS backend will only see the triples that have a specific known ABI. I'd like to stress that this process is the same as the one we already use today for other options. For example 'x86_64-linux-gnu-clang -m32' transforms the triple with get32BitArch...
2016 Jul 05
2
Representing MIPS ABI information in the triple as ARM/X86 do for EABI/EABIHF/X32
...pectively to transform the triple for the backend.
In summary, human end users of tools such as clang will continue using the same triples as they always have. These tools will then resolve them down to the effective triple (for example, in functions like clang's ComputeEffectiveClangTriple(), ComputeLLVMTriple(), and computeTargetTriple()). The MIPS backend will only see the triples that have a specific known ABI. I'd like to stress that this process is the same as the one we already use today for other options. For example 'x86_64-linux-gnu-clang -m32' transforms the triple with get32BitArch...
2012 Jul 22
12
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 22 July 2012 20:42, Anton Korobeynikov <anton at korobeynikov.info> wrote:
>> Any suggestions?
> Try to specify CPU explicitly.
He shouldn't have to, but that might help. Maybe setting -march? This
is a big mess...
I thought that v7 always assumed Thumb2 for the thumb flag, and v7M
should always assume Cortex-M3 CPU if none provided.
It's funny that James had a great