Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] llvm no build?"
2009 Mar 12
0
[LLVMdev] llvm no build?
Mike Stump wrote:
> llvm no build?
>
> llvm/llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp: In member function
> ‘bool llvm::PIC16AsmPrinter::printMachineInstruction(const
> llvm::MachineInstr*)’:
> llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp:80: error: ‘CurBank’ was not
> declared in this scope
> llvm/lib/Target/PIC16/PIC16AsmPrinter.cpp: In member function ‘virtual
>
2010 Jul 26
2
[LLVMdev] LLVM Dependency Graph
Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows.
digraph G {
ipo
2008 Sep 26
4
[LLVMdev] build failure in Attributes.h
I'm seeing a build failure...
In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/
Attributes.cpp:14:
/Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member
function 'llvm::Attributes
llvm::AttrListPtr::getParamAttributes(unsigned int) const':
/Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h:152: error:
'assert' was not declared in this scope
2008 Jan 02
1
[LLVMdev] problems found with make check on x86 darwin9
FAIL: /Volumes/mrs5/net/llvm/llvm/test/CFrontend/2007-09-20-
GcrootAttribute.c
Failed with exit(1) at line 3
while running: /Volumes/mrs5/Packages/llvm-2/bin/llvm-gcc -emit-llvm -
S -emit-llvm /Volumes/mrs5/net/llvm/llvm/test/CFrontend/2007-09-20-
GcrootAttribute.c -o - | llvm-as
llvm-as: assembly parsed, but does not verify as correct!
Enclosing function does not specify a collector algorithm.
2007 Dec 15
1
[LLVMdev] strict aliasing in SPU land
/Volumes/mrs5/net/llvm/llvm/llvm/lib/Target/CellSPU/
SPUISelDAGToDAG.cpp: In function
'bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*, short int&)':
/Volumes/mrs5/net/llvm/llvm/llvm/lib/Target/CellSPU/
SPUISelDAGToDAG.cpp:141: warning: dereferencing type-punned pointer
will break strict-aliasing rules
In file included from
2008 Sep 24
1
[LLVMdev] llvm broken?
/Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/CodeGenPrepare.cpp:
In member function
‘bool<unnamed>::CodeGenPrepare::OptimizeInlineAsmInst
(llvm::Instruction*, llvm::CallSite, llvm::DenseMap<llvm::Value*,
llvm::Value*, llvm::DenseMapInfo<llvm::Value*>,
llvm::DenseMapInfo<llvm::Value*> >&)’:
2008 Sep 26
0
[LLVMdev] build failure in Attributes.h
Works for me. Presumably #including <cassert> will fix it though?
On Sep 26, 2008, at 4:30 PMPDT, Mike Stump wrote:
> I'm seeing a build failure...
>
> In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/
> Attributes.cpp:14:
> /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member
> function 'llvm::Attributes
>
2009 Jan 02
2
[LLVMdev] new warnings in -r61596
2 new warnings in llvm:
/Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp: In member
function 'bool llvm::LLParser::ParseGlobal(const std::string&, const
char*, unsigned int, bool, unsigned int)':
/Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp:446: warning:
'IsConstant' may be used uninitialized in this function
2007 Dec 20
2
[LLVMdev] random warnings
They looked real enough to me:
/Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: In
function ‘bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*,
short int&)’:
/Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp:
148: warning: dereferencing type-punned pointer will break strict-
aliasing rules
2008 Aug 20
1
[LLVMdev] new warning in InstructionCombining.cpp
/Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/
InstructionCombining.cpp: In member function
‘llvm::Instruction*<unnamed>::InstCombiner::visitAnd
(llvm::BinaryOperator&)’:
/Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/
InstructionCombining.cpp:3597: warning: ‘RHSCC’ may be used
uninitialized in this function
/Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/
2008 Jan 30
2
[LLVMdev] no build, no joy
llvm[3]: Compiling SPUISelDAGToDAG.cpp for Debug build
In file included from /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/
SPUISelDAGToDAG.cpp:334:
/Volumes/mrs5/net/llvm/llvm-build/lib/Target/CellSPU/
SPUGenDAGISel.inc: In member function ‘llvm::SDNode*
SPUDAGToDAGISel::Emit_5(const llvm::SDOperand&, unsigned int, unsigned
int, llvm::MVT::ValueType, llvm::MVT::ValueType)’:
2009 Jul 01
2
[LLVMdev] llvmc for PIC16
The driver behaves differently when I run it by specifying absolute path
than when I run it with relative path.
See example
Relative:
i00202 at ubuntu:/tmp$ mcc16 --save-temps -dry-run hello.c./clang-cc -I
./include -triple=pic16- -emit-llvm-bc hello.c -o hello.bc-pqDR1Y
llvm-ld -link-as-library hello.bc-pqDR1Y -o tmp.bc-M1Rwip
llc -march=pic16 -f tmp.bc-M1Rwip -o tmp.s-DcVczP
gpasm -I ./inc
2009 Aug 12
4
[LLVMdev] XCore & PIC16 AsmPrinters
Hi XCore and PIC16 maintainers,
I'd appreciate it if you guys could move your AsmPrinter
implementation to be in a subdirectory like the rest of the other
targets (e.g. make it live in lib/Target/PIC16/AsmPrinter). Anton is
planning to move MSP430 to use the same approach. Having all the
targets use the same design simplifies the build system and keeps the
target architecture more
2007 Dec 15
4
[LLVMdev] fix warning with newer g++ compilers
Newer g++ compilers can emit:
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
function 'int llvm::LLLexer::LexAt()':
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp:287:
warning: suggest a space before ';' or explicit braces around empty
body in 'for' statement
/Volumes/mrs5/net/llvm/llvm/llvm/lib/AsmParser/LLLexer.cpp: In member
2009 Jul 20
2
[LLVMdev] PIC16TargetAsmInfo::getBSSSectionForGlobal
On Jul 20, 2009, at 4:18 PM, Alireza.Moshtaghi at microchip.com wrote:
> Substituting the uses of a global with an absolute address would make
> all accesses to that global through pointer, which is very inefficient
> on PIC16. So we don't change the code generation for that global;
> instead we only pass the address information to the linker (home made
> linker) through some
2007 Dec 15
2
[LLVMdev] strict aliasing warning in x86 land
/Volumes/mrs5/net/llvm/llvm/llvm/lib/Target/X86/X86ISelLowering.cpp:
In member function 'llvm::SDOperand
llvm::X86TargetLowering::LowerTRAMPOLINE(llvm::SDOperand,
llvm::SelectionDAG&)':
/Volumes/mrs5/net/llvm/llvm/llvm/lib/Target/X86/X86ISelLowering.cpp:
5305: warning: dereferencing type-punned pointer will break strict-
aliasing rules
:-(
2008 Jan 09
1
[LLVMdev] icing on LiveIntervalAnalysis
On darwin x86, I'm seeing:
$ make ENABLE_OPTIMIZED=1
llvm[2]: Compiling LiveIntervalAnalysis.cpp for Release build
Assertion failed: (MVT::isInteger(LVT)), function
MeetsMaxMemopRequirement, file /Volumes/mrs5/net/llvm/llvm/lib/CodeGen/
SelectionDAG/SelectionDAGISel.cpp, line 4230.
/Volumes/mrs5/net/llvm/llvm/lib/CodeGen/LiveIntervalAnalysis.cpp:1466:
internal compiler error: Abort trap
2009 Jan 24
1
[LLVMdev] new warnings
A new warning:
/Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp: In member
function 'bool llvm::LLParser::ParseGlobal(const std::string&, const
char*, unsigned int, bool, unsigned int)':
/Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp:448: warning:
'IsConstant' may be used uninitialized in this function
2009 Jul 21
0
[LLVMdev] PIC16TargetAsmInfo::getBSSSectionForGlobal
> My short term goal is to make TargetAsmInfo not depend on libvmcore.
> This means that no methods in it should take GlobalValue*'s for
> example. There is a suite of GV classification methods that need to
> be moved somewhere else, probably in TargetLowering or asmprinter. One
> method in particular (SectionForGlobal) is virtual and only re-
> implemented for
2011 May 10
0
[LLVMdev] llvm backend
Hi Roberto,
The PIC24 family of devices share very little commonality with PIC16 beyond the naming convention. They're a register-based 16-bit architecture, unlike the PIC16. That said, that does mean that LLVM is a much more reasonable fit to target the PIC24 (and dsPIC) than it is for PIC16.
Modeling your target files after the MSP430 or Blackfin backend is likely your best bet to get up