Displaying 3 results from an estimated 3 matches for "var_refs_queu".
Did you mean:
var_refs_queue
2004 May 05
0
[LLVMdev] Testing LLVM on OS X
...nction returns address of local variable
combine.c:2683: warning: function returns address of local variable
combine.c:2695: warning: function returns address of local variable
combine.c:2747: warning: function returns address of local variable
WARNING: Type conflict between types named 'struct.var_refs_queue'.
Src=' %struct.var_refs_queue'.
Dest=' %struct.var_refs_queue'
WARNING: Type conflict between types named 'struct.sequence_stack'.
Src=' %struct.sequence_stack'.
Dest=' %struct.sequence_stack'
WARNING: Type conflict between types named...
2004 May 04
6
[LLVMdev] Testing LLVM on OS X
On Tue, 4 May 2004, Chris Lattner wrote:
> I suspect that a large reason that LLVM does worst than a native C
> compiler with the CBE+GCC is that LLVM generates very low-level C code,
> and I'm not convinced that GCC is doing a very good job (ie, without
> syntactic loops).
Yup, this is EXACTLY what is going on.
I took this very simple C function:
int Array[1000];
void test(int
2004 May 05
2
[LLVMdev] Testing LLVM on OS X
...ss of local variable
> combine.c:2683: warning: function returns address of local variable
> combine.c:2695: warning: function returns address of local variable
> combine.c:2747: warning: function returns address of local variable
> WARNING: Type conflict between types named 'struct.var_refs_queue'.
> Src=' %struct.var_refs_queue'.
> Dest=' %struct.var_refs_queue'
> WARNING: Type conflict between types named 'struct.sequence_stack'.
> Src=' %struct.sequence_stack'.
> Dest=' %struct.sequence_stack'
> WARNING: Typ...