Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] problems found with make check on x86 darwin9"
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.
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)’:
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
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
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 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 Apr 28
3
[LLVMdev] getting started with IR needing GC
On Mon, Apr 21, 2008 at 8:13 PM, Gordon Henriksen
<gordonhenriksen at mac.com> wrote:
>
> Hi Terence,
>
>
> I think you're getting hung up on the details of the shadow stack collector.
> The shadow stack is a GC that is possible within this framework, but of
> course could be implemented without any special support. Its presence is
> more misleading than anything
2008 Apr 28
2
[LLVMdev] getting started with IR needing GC
On Sun, Apr 27, 2008 at 9:34 PM, Gordon Henriksen
<gordonhenriksen at mac.com> wrote:
> As for the compiler plugin interface, I suggest you ignore it
> initially and use the provided shadow-stack option for the time being.
> The shadow stack generates significantly suboptimal code, but will let
> you avoid writing some platform-specific code. Instead, simply copy
> the
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/
2007 Dec 22
0
[LLVMdev] random warnings
On Dec 20, 2007, at 3:56 PM, Mike Stump wrote:
> They looked real enough to me:
Fixed, thanks.
-Chris
>
>
> /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:
2008 Apr 28
0
[LLVMdev] getting started with IR needing GC
On 2008-04-27, at 21:29, Lane Schwartz wrote:
> Hi guys,
Hi Lane!
This is a lot of questions. I'm not going to answer each individually,
but will instead give general guidance to help you avoid the pain
points…
> I somehow need to inform the garbage collection runtime (my
> copycollector.c) about my variables - specifically about gc roots.
> So, after I get new memory
2008 Apr 28
0
[LLVMdev] getting started with IR needing GC
On Apr 28, 2008, at 14:28, Lane Schwartz wrote:
> On Sun, Apr 27, 2008 at 9:34 PM, Gordon Henriksen
> <gordonhenriksen at mac.com> wrote:
>
>> As for the compiler plugin interface, I suggest you ignore it
>> initially and use the provided shadow-stack option for the time
>> being. The shadow stack generates significantly suboptimal code,
>> but will
2008 Apr 22
0
[LLVMdev] getting started with IR needing GC
Hi Terence,
I think you're getting hung up on the details of the shadow stack
collector. The shadow stack is a GC that is possible within this
framework, but of course could be implemented without any special
support. Its presence is more misleading than anything else. Taking a
step back, the concepts are:
llvm.gcroot instructs the code generator --> My GC needs to be able to
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
2008 Nov 08
0
[LLVMdev] non-pointer gcroot
On Nov 7, 2008, at 15:29, Scott Graham wrote:
> I'm getting an assert in LowerIntrinsics::InsertRootInitializers
> because I'm gcroot'ing an alloca to a non-pointer.
>
> I was hoping to modify InsertRootInitializers to memset the
> structure in the case that it's not a pointer, but I'm not sure how
> to. Can anyone suggest what should go at "todo;