[prev in list] [next in list] [prev in thread] [next in thread] 

List:       llvm-dev
Subject:    [LLVMdev] Can't Figure Out My Error :(
From:       Reid Spencer <reid () x10sys ! com>
Date:       2004-03-28 19:03:59
Message-ID: 1080519819.25793.108.camel () bashful ! x10sys ! com
[Download RAW message or body]

[Attachment #2 (multipart/mixed)]

[Attachment #4 (multipart/alternative)]


The XPL compiler produced the attached OneOfEach.bc file without error
or warning from either LLVM or XPLC. However when I llvm-dis the file, I
get:

llvm-dis: Failed value look-up for name 'entry'

The Bytecode Reader prints this out when it can't find the associated
value for the name.  Obviously I botched something in the XPL compiler
but I would have thought the verified would catch my mistake before
writing the byte code. 

The patch to the Reader.cpp file that I sent you earlier added the "for
name 'entry'" part to the output. Unfortunately, this doesn't help
because my source input doesn't have a symbol named "entry". 

Any hints?

On Sun, 2004-03-28 at 15:58, Chris Lattner wrote:

> On Sun, 28 Mar 2004, Reid Spencer wrote:
> 
> > Would you like me to send the patches to sabre@nondot.org or have you
> > seen them already?
> 
> I haven't seen them.  Feel free to send them my way :)
> 
> -Chris



_______________________
Reid Spencer
President & CTO
eXtensible Systems, Inc.
rspencer@x10sys.com

[Attachment #7 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD>
<BODY>
The XPL compiler produced the attached OneOfEach.bc file without error or warning \
from either LLVM or XPLC. However when I llvm-dis the file, I get:<BR> <BR>
llvm-dis: Failed value look-up for name 'entry'<BR>
<BR>
The Bytecode Reader prints this out when it can't find the associated value for the \
name.&nbsp; Obviously I botched something in the XPL compiler but I would have \
thought the verified would catch my mistake before writing the byte code. <BR> <BR>
The patch to the Reader.cpp file that I sent you earlier added the &quot;for name \
'entry'&quot; part to the output. Unfortunately, this doesn't help because my source \
input doesn't have a symbol named &quot;entry&quot;. <BR> <BR>
Any hints?<BR>
<BR>
On Sun, 2004-03-28 at 15:58, Chris Lattner wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#301fe4"><I>On Sun, 28 Mar 2004, Reid Spencer wrote:

&gt; Would you like me to send the patches to sabre@nondot.org or have you
&gt; seen them already?

I haven't seen them.  Feel free to send them my way :)

-Chris</I></FONT></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
<BR>
<ADDRESS><FONT SIZE="4"><I>_______________________<BR>
Reid Spencer<BR>
President &amp; CTO<BR>
eXtensible Systems, Inc.<BR>
rspencer@x10sys.com</I></FONT></ADDRESS>
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>


["OneOfEach.bc" (OneOfEach.bc)]

llvm {
*!

 
		
"&%		
"&[OneOfEachhttp://xpl.org/XPL/examples/OneOfEach.xpl0.2.0				 \
2	 entry 2	
entry 2	
entryxpl.mod.identityxpl.OneOfEach.a_sig1xpl.mod.namexpl. \
mod.public.idxpl.mod.infoxpl.OneOfEach.a_sig2xpl.OneOfEach.a_sig3Alias \
ForIntxpl.OneOfEach.any_atomxpl.OneOfEach.array_10x10x10xpl.OneOfEach.boolean_at \
omxpl.OneOfEach.byte_atomxpl.OneOfEach.character_atomxpl.OneOfEach.double_atom \
xpl.OneOfEach.enumeration_atomxpl.OneOfEach.int_atomxpl.OneOfEach.integer_atomxp \
l.OneOfEach.interval_atom	xpl.OneOfEach.long_atom	xpl.OneOfEach.octet_atomxpl.OneO \
fEach.range_atomxpl.OneOfEach.real_atom"xpl.OneOfEach.reference_atomxpl.OneOfEach \
.short_atomxpl.OneOfEach.sig1xpl.OneOfEach.sig2xpl.OneOfEach.sig3#xpl.OneOfEach.sig4$xpl.OneOfEach.sig5
 xpl.OneOfEach.single_atom'xpl.OneOfEach.stricture&xpl.OneOfEach.text_atomxpl.One \
OfEach.ubyte_atomxpl.OneOfEach.uint_atomxpl.OneOfEach.ulong_atomxpl.OneOfEach.ushort_atomxpl.OneOfEach.void_atomxpl.mod.info.type



["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic