search for: targetsubtarget

...c/llvm2.6/include/llvm/Target/TargetInstrInfo.h:474: undefined reference to `llvm::TargetInstrInfo::~TargetInstrInfo()' ../../lib/libLLVMAVRCodeGen.a(AVRTargetMachine.cpp.o): In function `~AVRSubtarget': /home/john/src/llvm2.6/lib/Target/AVR/AVRSubtarget.h:24: undefined reference to `llvm::TargetSubtarget::~TargetSubtarget()' /home/john/src/llvm2.6/lib/Target/AVR/AVRSubtarget.h:24: undefined reference to `llvm::TargetSubtarget::~TargetSubtarget()' ../../lib/libLLVMAVRCodeGen.a(AVRTargetMachine.cpp.o): In function `~LLVMTargetMachine': /home/john/src/llvm2.6/include/llvm/Target/TargetM...

What's the purpose of the TargetSubtarget class? It appears the only users of getSubtarget are in the target-specific code, where the abstraction is superfluous. Is it just a way to encourage targets to follow a nice pattern of keeping subtarget state in a separate class, or are there grand plans? Dan -- Dan Gohman, Cray Inc.

...Return 0 int BytesCallerReserves 0 int - Subtarget 0x00000000008eda90 {AsmFlavor=Intel PICStyle=None X86SSELevel=SSE2 ...} const llvm::X86Subtarget * + llvm::TargetSubtarget {...} llvm::TargetSubtarget AsmFlavor Intel llvm::X86Subtarget::AsmWriterFlavorTy PICStyle None llvm::PICStyle::Style X86SSELevel SSE2 llvm::X8...

...::SDValue>, llvm::DenseMapInfo<unsigned int> >&, bool, bool, bool)in libLLVMSelectionDAG.a(InstrEmitter.cpp.o) llvm::DAGTypeLegalizer::ExpandRes_BIT_CONVERT(llvm::SDNode*, llvm::SDValue&, llvm::SDValue&)in libLLVMSelectionDAG.a(LegalizeTypesGeneric.cpp.o) "llvm::TargetSubtarget::enablePostRAScheduler(llvm::CodeGenOpt::Level, llvm::TargetSubtarget::AntiDepBreakMode&, llvm::SmallVectorImpl<llvm::TargetRegisterClass*>&) const", referenced from: vtable for llvm::EBCSubtargetin libLLVMEBCCodeGen.a(EBCTargetMachine.cpp.o) vtable for llvm::EBCSubta...

...::SDValue>, llvm::DenseMapInfo<unsigned int> >&, bool, bool, bool)in libLLVMSelectionDAG.a(InstrEmitter.cpp.o) llvm::DAGTypeLegalizer::ExpandRes_BIT_CONVERT(llvm::SDNode*, llvm::SDValue&, llvm::SDValue&)in libLLVMSelectionDAG.a(LegalizeTypesGeneric.cpp.o) "llvm::TargetSubtarget::enablePostRAScheduler(llvm::CodeGenOpt::Level, llvm::TargetSubtarget::AntiDepBreakMode&, llvm::SmallVectorImpl<llvm::TargetRegisterClass*>&) const", referenced from: vtable for llvm::EBCSubtargetin libLLVMEBCCodeGen.a(EBCTargetMachine.cpp.o) vtable for llvm::EBCSubta...

On Wed, Feb 23, 2011 at 2:46 AM, Chris Lattner <clattner at apple.com> wrote: > > There is recently a discussion on the LLDB list about how to deal with targets, and our current mismash of llvm::Triple and the various subclasses of TargetSubtarget leave a lot to be desired.  GNU target triples are really important as input devices to the compiler (users want to specify them) but they aren't detailed enough for internal clients. > > Anyway, in short, I think that we should unify the variety of code we have to deal with this stuff in...

On Feb 12, 2008, at 5:26 PM, Chuck Rose III wrote: > Hola LLVMers, > > I’m debugging through some strangeness that I’m seeing on X64 on > windows with LLVM2.2. I had to change the code so that it would > engage the x64 target machine on windows builds, but I’ve otherwise > left LLVM 2.2 alone. The basic idea is that I’ve got a function bar > which is compiled by

...ully functional and off the 'beta' list. Major Code Generator Changes: X. Nate wrote a new component for the backend, a DAG Combiner. This allows the backend to take advantage of identities and do low-level peephole-style optimizations on the DAG. X. Nate added support for a new TargetSubtarget interface, which determines which parts of the target to enable based on the target-triple (e.g., whether to use GAS or Intel asm printers on X86). X. Jim Laskey extended sub-target support to include -mcpu and -mattr, allowing the target to think about what to do when particular featur...

Hi All, There is recently a discussion on the LLDB list about how to deal with targets, and our current mismash of llvm::Triple and the various subclasses of TargetSubtarget leave a lot to be desired. GNU target triples are really important as input devices to the compiler (users want to specify them) but they aren't detailed enough for internal clients. Anyway, in short, I think that we should unify the variety of code we have to deal with this stuff into a new...

I got bit by this in LLVM 2.4 DagCombiner.cpp and it's still in trunk: SDValue DAGCombiner::visitSTORE(SDNode *N) { [...] // If this is a store of a bit convert, store the input value if the // resultant store does not need a higher alignment than the original. if (Value.getOpcode() == ISD::BIT_CONVERT && !ST->isTruncatingStore() && ST->isUnindexed()) {

...' list. > > > Major Code Generator Changes: > > X. Nate wrote a new component for the backend, a DAG Combiner. This > allows the backend to take advantage of identities and do low-level > peephole-style optimizations on the DAG. > X. Nate added support for a new TargetSubtarget interface, which > determines which parts of the target to enable based on the > target-triple (e.g., whether to use GAS or Intel asm printers on X86). > X. Jim Laskey extended sub-target support to include -mcpu and -mattr, > allowing the target to think about what to do wh...

Hola LLVMers, I'm debugging through some strangeness that I'm seeing on X64 on windows with LLVM2.2. I had to change the code so that it would engage the x64 target machine on windows builds, but I've otherwise left LLVM 2.2 alone. The basic idea is that I've got a function bar which is compiled by VStudio and I'm creating another function foo via LLVM JIT which is going

...unctional and off the 'beta' list. Major Code Generator Changes: 6. Nate wrote a new component for the backend, a DAG Combiner. This allows the backend to take advantage of identities and do low-level peephole-style optimizations on the DAG. 7. Nate added support for a new TargetSubtarget interface, which determines which parts of the target to enable based on the target-triple (e.g., whether to use GAS or Intel asm printers on X86). 8. Jim Laskey extended sub-target support to include -mcpu and -mattr, allowing the target to think about what to do when particular f...

...TargetSchedule.td -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetSelect.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetSelectionDAG.td -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetSelectionDAGInfo.h -- Installing: /usr/local/llvm-2.8/include/llvm/Target/TargetSubtarget.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/IPO -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/IPO/InlinerPass.h -- Installing: /usr/local/llvm-2.8/include/llvm/Transforms/IPO.h -- Installing: /usr/local/llvm-2....

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel

...> +// > +// This file is distributed under the University of Illinois Open Source > +// License. See LICENSE.TXT for details. > +// > +//==-----------------------------------------------------------------------===// > +// > +// This file declares the AMDGPU specific subclass of TargetSubtarget. > +// > +//===----------------------------------------------------------------------===// > + > +#ifndef _AMDGPUSUBTARGET_H_ > +#define _AMDGPUSUBTARGET_H_ > +#include "AMDILSubtarget.h" > + > +namespace llvm { > + > +class AMDGPUSubtarget : public AMDILSubt...