Displaying 5 results from an estimated 5 matches for "vendortyp".
Did you mean:
vendortype
2014 Jul 09
5
[LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
...num 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 {
UnknownVendor,
@@ -104,7 +89,8 @@
BGQ,
Freescale,
IBM,
- NVIDIA
+ NVIDIA,
+ CSR
};
enum OSType {
UnknownOS,
@@ -164,9 +150,6 @@
/// The parsed arch type.
ArchType Arch;
- /// The parsed subarchitecture type.
- SubArchType SubArch;
-...
2014 Jun 24
2
[LLVMdev] [cfe-dev] [PATCH] triples for baremetal
Hi Jonathan,
This looks a bit odd. Any reason for the unknown->none conflating in
this way? For most (all) of the ports unknown-elf works the same as
none-elf. I'm also not sure if someone decided to have,
arm-codesourcery-elf that this would still work with the patch.
Thoughts?
-eric
On Tue, Jun 24, 2014 at 7:35 AM, Amara Emerson <amara.emerson at gmail.com> wrote:
> Hi Jon,
2014 Jul 10
2
[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 VendorType {
UnknownVendor,
@@ -89,7 +90,8 @@
Freescale,
IBM,
ImaginationTechnologies,
- NVIDIA
+ NVIDIA,
+ CSR
};
enum OSType {
UnknownOS,
Index: lib/Support/Triple.cpp
===================================================================
--- lib/Support/Triple.c...
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,
>> -
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