search for: mipsgensubtargetinfo

...reated files for fast-isel? If I make the following change to Makefile in lib/Target/Mips BUILT_SOURCES = MipsGenRegisterInfo.inc MipsGenInstrInfo.inc \ MipsGenAsmWriter.inc MipsGenCodeEmitter.inc \ MipsGenDAGISel.inc MipsGenCallingConv.inc \ - MipsGenSubtargetInfo.inc MipsGenMCCodeEmitter.inc \ + MipsGenSubtargetInfo.inc MipsGenFastISel.inc MipsGenMCCodeEmitter.inc \ MipsGenDisassemblerTables.inc \ MipsGenMCPseudoLowering.inc MipsGenAsmMatcher.inc I get an error. Included from /home/rkotler/workspace/llv...

...en-instr-info) tablegen(LLVM MipsGenCodeEmitter.inc -gen-emitter) tablegen(LLVM MipsGenMCCodeEmitter.inc -gen-emitter -mc-emitter) tablegen(LLVM MipsGenAsmWriter.inc -gen-asm-writer) tablegen(LLVM MipsGenDAGISel.inc -gen-dag-isel) tablegen(LLVM MipsGenCallingConv.inc -gen-callingconv) tablegen(LLVM MipsGenSubtargetInfo.inc -gen-subtarget) add_public_tablegen_target(MipsCommonTableGen) When I started trying to generate MipsGenAsmMatcher.inc for the assembler I started getting errors. tblgen -gen-asm-matcher -I ~/workarea/asm/llvm/include/ Mips.tdIncluded from Mips.td:24: MipsInstrInfo.td:833:14: error: Instruct...

...LVM MipsGenCodeEmitter.inc -gen-emitter) > tablegen(LLVM MipsGenMCCodeEmitter.inc -gen-emitter -mc-emitter) > tablegen(LLVM MipsGenAsmWriter.inc -gen-asm-writer) > tablegen(LLVM MipsGenDAGISel.inc -gen-dag-isel) > tablegen(LLVM MipsGenCallingConv.inc -gen-callingconv) > tablegen(LLVM MipsGenSubtargetInfo.inc -gen-subtarget) > add_public_tablegen_target(MipsCommonTableGen) > > When I started trying to generate MipsGenAsmMatcher.inc for the assembler I started getting errors. > > tblgen -gen-asm-matcher -I ~/workarea/asm/llvm/include/ Mips.tdIncluded from Mips.td:24: > MipsInstrI...

Jim, You are correct: MipsSubtarget. For llvm-mc we have a straight MCSubtargetInfo object. For llc we get a MipsSubtarget object which derives from MipsGenSubtargetInfo which derives from TargetSubtargetInfo which derives from MCSubtargetInfo. The patch I hope to send out for review will do this: Add a new data member to MCSubtargetInfo base class. It will be a set of integers that is used or not by targets to post flags that otherwise cannot be stored equally b...

.../Function.h" +#include "llvm/Support/CommandLine.h" +#include "llvm/Support/Debug.h" #include "llvm/Support/TargetRegistry.h" +#include "llvm/Support/raw_ostream.h" #define GET_SUBTARGETINFO_TARGET_DESC #define GET_SUBTARGETINFO_CTOR #include "MipsGenSubtargetInfo.inc" + using namespace llvm; +static cl::opt<bool> Mixed16_32( + "mips-mixed-16-32", + cl::init(false), + cl::desc("Allow for a mixture of Mips16 " + "and Mips32 code in a single source file"), + cl::Hidden); + void MipsSubtarget::anchor(...

On Thu, Mar 28, 2013 at 12:22 PM, Nadav Rotem <nrotem at apple.com> wrote: > IMHO the right way to handle target function attributes is to > re-initialize the target machine and TTI for every function (if the > attributes changed). Do you have another solution in mind ? I don't really understand this. TargetMachine and TTI may be quite expensive to initialize. Doing so for

...> > > > I'm a little concerned this might break the shared library ABI. We will need > to verify that it doesn't before it gets merged. I don't think this will break it since the two functions that are changed are private to MipsAsmParser and our Feature* constants in MipsGenSubtargetInfo.inc are already uint64_t. However, I haven't supported a shared library ABI before so I can't be sure. How would I check? > > * r218745 - [mips] Fix disassembly of [ls][wd]c[23], cache, and pref > > > > This looks OK to me. Thanks. > > I'd also like t...

...Jim Grosbach Cc: Rafael Espíndola; List Subject: RE: [LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter Jim, You are correct: MipsSubtarget. For llvm-mc we have a straight MCSubtargetInfo object. For llc we get a MipsSubtarget object which derives from MipsGenSubtargetInfo which derives from TargetSubtargetInfo which derives from MCSubtargetInfo. The patch I hope to send out for review will do this: Add a new data member to MCSubtargetInfo base class. It will be a set of integers that is used or not by targets to post flags that otherwise cannot be stored equally b...

.../Mips/.gitignore @@ -0,0 +1,12 @@ +MipsGenAsmMatcher.inc +MipsGenAsmWriter.inc +MipsGenCallingConv.inc +MipsGenCodeEmitter.inc +MipsGenDAGISel.inc +MipsGenDisassemblerTables.inc +MipsGenEDInfo.inc +MipsGenInstrInfo.inc +MipsGenMCCodeEmitter.inc +MipsGenMCPseudoLowering.inc +MipsGenRegisterInfo.inc +MipsGenSubtargetInfo.inc diff --git a/lib/Target/NVPTX/.gitignore b/lib/Target/NVPTX/.gitignore new file mode 100644 index 0000000..74001d1 --- /dev/null +++ b/lib/Target/NVPTX/.gitignore @@ -0,0 +1,5 @@ +NVPTXGenAsmWriter.inc +NVPTXGenDAGISel.inc +NVPTXGenInstrInfo.inc +NVPTXGenRegisterInfo.inc +NVPTXGenSubtargetInfo....

On Dec 10, 2012, at 1:15 PM, "Carter, Jack" <jcarter at mips.com> wrote: > Here are some examples using the gnu assembler reacting to the same input file with different commandline options. > > These are using the GCC assembler on hello.c > // abi o32, arch mips32r2, relocation model pic+cpic > mips-linux-gnu-as -mips32r2 -EL -KPIC -o hello_gas.o hello_gas.s >

Hi, I'd like to propose the following patches for inclusion in Clang 3.5.1. Proposed clang patches: * r213769 - Fix test/Driver/cl-x86-flags.c by providing explicit -target * r214025 - [Driver][Mips] Check output of -dynamic-linker arguments by the Clang driver * r214662 - [Mips] Add the `mips64-linux-gnu` target to the test case to check `in128` type handling. *

Here are some examples using the gnu assembler reacting to the same input file with different commandline options. These are using the GCC assembler on hello.c // abi o32, arch mips32r2, relocation model pic+cpic mips-linux-gnu-as -mips32r2 -EL -KPIC -o hello_gas.o hello_gas.s e_flags 0x70001007 EF_MIPS_NOREORDER EF_MIPS_PIC EF_MIPS_CPIC E_MIPS_ABI_O32 EF_MIPS_ARCH_32R2 // abi