[LLVMdev] Representing the dependencies of a bitcode module
Chris Lattner
sabre at nondot.org
Mon Apr 28 21:01:54 PDT 2008
On Apr 28, 2008, at 8:21 PM, Talin wrote:
> However, I notice that getting access to the strings from within the
> command-line tool is a little complicated, since I have to decompose
> the
> various constant getElementPtr expressions in order to get at the
> actual
> string. I'm wondering if there's a better way to represent this
> information. Maybe using the debug API, or perhaps annotation
> intrinsics?
There isn't a good interface to the annotation intrinsics yet, it
would be nice to have them, then this could be encoded as annotations.
-Chris
More information about the llvm-dev
mailing list