search for: unknownarch

In particular, I would for example like to prevent that two fields of type i32 are packed into an i64 parameter. And so on... Thanks! -- Zvonimir

...dia"; + case CSR: return "csr"; } llvm_unreachable("Invalid VendorType!"); @@ -208,6 +211,7 @@ .Case("amdil", amdil) .Case("spir", spir) .Case("spir64", spir64) + .Case("kalimba", kalimba) .Default(UnknownArch); } @@ -281,6 +285,7 @@ .Case("amdil", Triple::amdil) .Case("spir", Triple::spir) .Case("spir64", Triple::spir64) + .Case("kalimba", Triple::kalimba) .Default(Triple::UnknownArch); } @@ -295,6 +300,7 @@ .Case("ibm&q...

...dia"; + case CSR: return "csr"; } llvm_unreachable("Invalid VendorType!"); @@ -207,6 +210,7 @@ .Case("amdil", amdil) .Case("spir", spir) .Case("spir64", spir64) + .Case("kalimba", kalimba) .Default(UnknownArch); } @@ -280,6 +284,7 @@ .Case("amdil", Triple::amdil) .Case("spir", Triple::spir) .Case("spir64", Triple::spir64) + .Case("kalimba", Triple::kalimba) .Default(Triple::UnknownArch); } @@ -293,6 +298,7 @@ .Case("fsl&q...

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, >> -

...eader will read this. But I have no idea where to write it now. 2. In CoverageMapping.cpp, there is a checking “OF->getArch() != Triple(Arch).getArch()” and it makes an error if not equal. “OF->getArch” will go into a switch/case and the code enters the default branch which returns an UnknownArch. I hacked the code to make default branch return Triple::XXXX(only a temporary solution for the first point). Where should I place __llvm_prf_* sections? Is it ok to put them into .rodata section? Best, Ruobin 发件人: vsk at apple.com [mailto:vsk at apple.com] 代表 Vedant Kumar 发送时间: 2019年1月25日 3:14...

...ronment()); - T = Triple("arm-none-none-eabi"); - EXPECT_EQ(Triple::arm, T.getArch()); - EXPECT_EQ(Triple::UnknownVendor, T.getVendor()); - EXPECT_EQ(Triple::UnknownOS, T.getOS()); - EXPECT_EQ(Triple::EABI, T.getEnvironment()); - T = Triple("huh"); EXPECT_EQ(Triple::UnknownArch, T.getArch()); } @@ -246,7 +240,7 @@ EXPECT_EQ("i486--linux-gnu", Triple::normalize("i486-linux-gnu")); // i486-pc-linux-gnu EXPECT_EQ("i386-redhat-linux", Triple::normalize("i386-redhat-linux")); // i386-redhat-linux-gnu EXPECT_EQ("i686--linux...

...s that the API-user (e.g. clang) is expected to normalize such triples down to one of Triple::GNUABI32/GNUABIN32/GNUABI64. This can be as simple as adding: Triple ABITriple = TT.getABIVariant(ABIName); // ABIName can be the empty string to get the default ABI. if (ABITriple.getArch() != Triple::UnknownArch) { TT = ABITriple; ABIName = ""; // <- Only needed if this would end up in MCTargetOptions::ABIName. } to the appropriate place in the caller. This is the same way clang handles the -m32, -m64, -EL, and -EB options with those options using get32BitArchVariant(), get64BitArchV...

[+llvmdev, -llvm-dev] (Oopsies, llvmdev doesn't have a hyphen in it like all the others do) On 6/17/14, 10:45 AM, Jonathan Roelofs wrote: > [+llvm-dev, cfe-dev] > > Was "Re: [PATCH] ARM: allow inline atomics on Cortex M" > > On 6/17/14, 10:42 AM, Jonathan Roelofs wrote: >> >> >> On 6/17/14, 9:35 AM, Renato Golin wrote: >>> On 17 June 2014

...s that the API-user (e.g. clang) is expected to normalize such triples down to one of Triple::GNUABI32/GNUABIN32/GNUABI64. This can be as simple as adding: Triple ABITriple = TT.getABIVariant(ABIName); // ABIName can be the empty string to get the default ABI. if (ABITriple.getArch() != Triple::UnknownArch) { TT = ABITriple; ABIName = ""; // <- Only needed if this would end up in MCTargetOptions::ABIName. } to the appropriate place in the caller. This is the same way clang handles the -m32, -m64, -EL, and -EB options with those options using get32BitArchVariant(), get64BitArchV...

...10, 5)) @@ -699,7 +710,7 @@ void MCObjectFileInfo::InitMCObjectFileInfo(StringRef TT, Reloc::Model relocm, if ((Arch == Triple::x86 || Arch == Triple::x86_64 || Arch == Triple::arm || Arch == Triple::thumb || Arch == Triple::ppc || Arch == Triple::ppc64 || - Arch == Triple::UnknownArch) && + Arch == Triple::UnknownArch || Arch == Triple::aarch64) && (T.isOSDarwin() || T.getEnvironment() == Triple::MachO)) { Env = IsMachO; InitMachOMCObjectFileInfo(T); diff --git a/lib/Target/AArch64/AArch64AsmPrinter.cpp b/lib/Target/AArch64/AArch64AsmPrinte...

Hi vedant, 1. The definition is from llvm/Supprot/ELF.h. But this machine information(e_machine) is given to compiler at lib/MC/ELFObjectWriter.cpp. I greped the whole llvm project and found that e_machine was assigned at only two files. One was lib/MC/ELFObjectWriter.cpp(there was an comment said “e_machine=target”) and the other was tools/obj2yaml/elf2yaml.cpp(GDB stopped only at the

...Normalize the triple · Construct a llvm::Target o If the triple is not given, we fetch the default o We normalize the triple o We call TargetRegistry::lookupTarget() to get a llvm::Target. § If –march is given, and Triple::getArchTypeForLLVMName() doesn't return Triple::UnknownArch, the new arch this mutates the triple. Otherwise it applies the –march correctly but doesn't change the triple to match. In this way, it's possible to end up with i586-linux-gnu targeting the foobar architecture. · Call createMCRegInfo() · Call createMCAsmInfo() o MipsM...

...Normalize the triple • Construct a llvm::Target o If the triple is not given, we fetch the default o We normalize the triple o We call TargetRegistry::lookupTarget() to get a llvm::Target. • If –march is given, and Triple::getArchTypeForLLVMName() doesn't return Triple::UnknownArch, the new arch this mutates the triple. Otherwise it applies the –march correctly but doesn't change the triple to match. In this way, it's possible to end up with i586-linux-gnu targeting the foobar architecture. • Call createMCRegInfo() • Call createMCAsmInfo() o MipsM...

...Normalize the triple • Construct a llvm::Target o If the triple is not given, we fetch the default o We normalize the triple o We call TargetRegistry::lookupTarget() to get a llvm::Target. • If –march is given, and Triple::getArchTypeForLLVMName() doesn't return Triple::UnknownArch, the new arch this mutates the triple. Otherwise it applies the –march correctly but doesn't change the triple to match. In this way, it's possible to end up with i586-linux-gnu targeting the foobar architecture. • Call createMCRegInfo() • Call createMCAsmInfo() o MipsM...

...Normalize the triple • Construct a llvm::Target o If the triple is not given, we fetch the default o We normalize the triple o We call TargetRegistry::lookupTarget() to get a llvm::Target. • If –march is given, and Triple::getArchTypeForLLVMName() doesn't return Triple::UnknownArch, the new arch this mutates the triple. Otherwise it applies the –march correctly but doesn't change the triple to match. In this way, it's possible to end up with i586-linux-gnu targeting the foobar architecture. • Call createMCRegInfo() • Call createMCAsmInfo() o MipsM...

...Normalize the triple • Construct a llvm::Target o If the triple is not given, we fetch the default o We normalize the triple o We call TargetRegistry::lookupTarget() to get a llvm::Target. • If –march is given, and Triple::getArchTypeForLLVMName() doesn't return Triple::UnknownArch, the new arch this mutates the triple. Otherwise it applies the –march correctly but doesn't change the triple to match. In this way, it's possible to end up with i586-linux-gnu targeting the foobar architecture. • Call createMCRegInfo() • Call createMCAsmInfo() o MipsM...

...Normalize the triple • Construct a llvm::Target o If the triple is not given, we fetch the default o We normalize the triple o We call TargetRegistry::lookupTarget() to get a llvm::Target. • If –march is given, and Triple::getArchTypeForLLVMName() doesn't return Triple::UnknownArch, the new arch this mutates the triple. Otherwise it applies the –march correctly but doesn't change the triple to match. In this way, it's possible to end up with i586-linux-gnu targeting the foobar architecture. • Call createMCRegInfo() • Call createMCAsmInfo() o MipsM...

>> Here's the line of thought that I'd like people to start with: >> * Triples don't describe the target. They look like they should, but they >> don't. They're really just arbitrary strings. > >Triples are used as a starting point, but no more. I disagree with this but for now let's assume it's true. The starting point is incorrect because