search for: parsearmtripl

Displaying 4 results from an estimated 4 matches for "parsearmtripl".

Did you mean: parsearmtriple
2012 Mar 02
2
[LLVMdev] "-march" trashing ARM triple
ARM subtarget features are determined by parsing the target tuple string TT. (ParseARMTriple(StringRef TT) in ARMMCTargetDesc.cpp) In llc, the -march setting overrides the architecture specified in -mtriple. So when you invoke: $ llc -march arm -mtriple armv7-none-linux ... ParseARMTriple() will see TT == "arm-none-linux" instead of "armv7-none-linux". As a result,...
2012 Mar 02
0
[LLVMdev] "-march" trashing ARM triple
On Mar 2, 2012, at 12:04 AM, David Meyer <pdox at google.com> wrote: > ARM subtarget features are determined by parsing the target tuple string TT. (ParseARMTriple(StringRef TT) in ARMMCTargetDesc.cpp) > > In llc, the -march setting overrides the architecture specified in -mtriple. So when you invoke: > > $ llc -march arm -mtriple armv7-none-linux ... > > ParseARMTriple() will see TT == "arm-none-linux" instead of "armv7-n...
2014 Sep 05
2
[LLVMdev] HELP! Recent failure on llvm buildbot
...Wswitch] > switch (triple.getSubArch()) { > This is a warning turned into an error by -Werror. LLVM’s code should > be warning free. > You indeed added these entries to the enum and they seem not to be > handled in ARMMCTargetDesc.cpp. If you don’t know how to add these > to ParseARMTriple(), I’d suggest you revert your change until someone > with ARM MC knowledge helps you out. > > Fred > >> On 05 Sep 2014, at 09:43, Matthew Gardiner <mg11 at csr.com >> <mailto:mg11 at csr.com>> wrote: >> >> I'm working on lldb. >> >&gt...
2014 Sep 05
4
[LLVMdev] HELP! Recent failure on llvm buildbot
I'm working on lldb. I've just submitted a very small change (r217229) to Triple.h/.cpp. Soon after I get a mail subject: buildbot failure in LLVM on lld-x86_64-darwin13 Details: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Blamelist: mg11 My small change certainly did not cause lldb's build to fail on my machine. I looked into the build-log: