Displaying 7 results from an estimated 7 matches for "subarchtyp".
Did you mean:
subarchtype
2016 Jan 03
2
Diff to add ARMv6L to Target parser
...:
static llvm::Triple computeTargetTriple(StringRef DefaultTargetTriple) {
llvm::Triple triple = llvm::Triple(DefaultTargetTriple);
// Canonicalization of all armv6 sub architectures to armv6
if (triple.getArch() == llvm::Triple::ArchType::arm) {
if (triple.getSubArch() == llvm::Triple::SubArchType::ARMSubArch_v6 ||
triple.getSubArch() == llvm::Triple::SubArchType::ARMSubArch_v6m ||
triple.getSubArch() == llvm::Triple::SubArchType::ARMSubArch_v6k ||
triple.getSubArch() == llvm::Triple::SubArchType::ARMSubArch_v6t2) {
triple.setArchName("armv6");
}...
2014 Aug 19
2
[LLVMdev] llvm::Triple support for haswell-enabled x86_64
...LDB and we have a bunch of code that is manually
manipulating triples and doing a bunch of nasty stuff to account for the
fact that llvm::Triple doesn't currently have a way to detect x86_64h.
Is this something that llvm::Triple could be modified to support? Either
as a new ArchType, or a new SubArchType?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140819/4e3f3ff1/attachment.html>
2014 Jul 09
5
[LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
...// amdil: amd IL
spir, // SPIR: standard portable IR for OpenCL 32-bit version
- spir64 // SPIR: standard portable IR for OpenCL 64-bit version
+ spir64, // SPIR: standard portable IR for OpenCL 64-bit version
+ kalimba // Kalimba: generic kalimba
};
- enum SubArchType {
- NoSubArch,
-
- ARMSubArch_v8,
- ARMSubArch_v7,
- ARMSubArch_v7em,
- ARMSubArch_v7m,
- ARMSubArch_v7s,
- ARMSubArch_v6,
- ARMSubArch_v6m,
- ARMSubArch_v6t2,
- ARMSubArch_v5,
- ARMSubArch_v5te,
- ARMSubArch_v4t,
- ARMSubArch_v4
- };
enum VendorType {...
2014 Jul 09
2
[LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
On 7/9/14, 12:33 PM, Eric Christopher wrote:
> Any reason why you deleted code that isn't related?
>
> -eric
>
>> - enum SubArchType {
>> - NoSubArch,
>> -
>> - ARMSubArch_v8,
>> - ARMSubArch_v7,
>> - ARMSubArch_v7em,
>> - ARMSubArch_v7m,
>> - ARMSubArch_v7s,
>> - ARMSubArch_v6,
>> - ARMSubArch_v6m,
>> - ARMSubArch_v6t2,
>> - ARMSubA...
2014 Aug 19
2
[LLVMdev] llvm::Triple support for haswell-enabled x86_64
...ple, so what do I need to do to ensure that I don't break anyone else
who is running one of these systems and previously had a different default
triple?
On Tue, Aug 19, 2014 at 4:53 PM, Jim Grosbach <grosbach at apple.com> wrote:
> Sure, go for it. It’d be a fairly natural fit for a SubArchType.
>
>
>
> > On Aug 19, 2014, at 2:44 PM, Zachary Turner <zturner at google.com> wrote:
> >
> > I'm working on LLDB and we have a bunch of code that is manually
> manipulating triples and doing a bunch of nasty stuff to account for the
> fact that llvm::Tri...
2014 Jul 10
2
[LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
...n Wed, Jul 9, 2014 at 11:39 AM, Jonathan Roelofs
> <jonathan at codesourcery.com> wrote:
>>
>> On 7/9/14, 12:33 PM, Eric Christopher wrote:
>>> Any reason why you deleted code that isn't related?
>>>
>>> -eric
>>>
>>>> - enum SubArchType {
>>>> - NoSubArch,
>>>> -
>>>> - ARMSubArch_v8,
>>>> - ARMSubArch_v7,
>>>> - ARMSubArch_v7em,
>>>> - ARMSubArch_v7m,
>>>> - ARMSubArch_v7s,
>>>> - ARMSubArch_v6,
>>>> -...
2015 Jul 29
5
[LLVMdev] The Trouble with Triples
>
> The Triple object will remain unchanged.
>
> The Tuple will be the API to handle getting/setting parameters
> depending on the Triple, compiler flags, attributes, etc.
>
>
This part doesn't seem obvious from the direction the patches are going.
> There will be no string representation of all options, as that would
> be impossible, or at least, highly