Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] Question about the GraphWriter.h file"
2002 Nov 14
1
[LLVMdev] problem checking out llvm
When I check out llvm this morning. I got this error, so I couldn't check
out. Looks like the disk is full.. Please let me know how to fix this
problem.
Thanks,
xiaodong
xli3|csil-suna33|/usr/dcs/projects/cs426/xli3/llvm|[10]% cvs update
cvs update: Updating .
? gnumake.out
cvs update: Updating Support
cvs update: Updating include
cvs update: Updating include/Support
cvs update: cannot close
2002 Oct 27
2
[LLVMdev] Compile error in include/Support/GraphWriter.h
Issue: GraphWriter includes <ostream>, which my gcc2 apparently thinks
is <ostream.h>.
Fix: Make a new <Support/ostream> that handles this discrepancy, ala
<Support/hash_set>.
--
Casey Carter
Casey at Carter.net
ccarter at uiuc.edu
AIM: cartec69
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
URL:
2008 Sep 15
2
[LLVMdev] DOTGraphTraits and GraphWriter
Hi all,
I have two questions related to .dot graph output. Basically, I have a
graph representing a program dependence graph like structure with
(a) multiple edges between the same pair of nodes
(b) each edge having a special (different) text/label
I implemented a template-specialized version of DotGraphTraits for the
my graph structure which given a node, uses a map_iterator (similar to
the one
2008 Sep 16
0
[LLVMdev] DOTGraphTraits and GraphWriter
Hello Prakash,
The SelectionDAG viewers (llc -view-isel-dags etc.) support
both multiple edges between the same pair of nodes, and labels
at least for each incoming edge. See
lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp for code you
might use as an example, though it is a bit tricky.
Dan
On Sep 15, 2008, at 3:15 PM, Prakash Prabhu wrote:
> Hi all,
>
> I have two questions related
2008 Sep 16
2
[LLVMdev] DOTGraphTraits and GraphWriter
Hi Dan,
Thanks for the reply. I got the labels for each outgoing edge (at the
source node's 'structure' field) working. Is there a way to find out
the outgoing edge number from EdgeIter. (Basically the Node in my
graph has a a bunch of outgoing edges, so that I can just index into
that collection within the node to get the appropriate edges'
attributes).
regards,
Prakash
On Tue,
2008 Sep 22
0
[LLVMdev] DOTGraphTraits and GraphWriter
Hi Prakash,
I don't know of an easy way to do this, other than to use random-access
iterators so you can compute the distance between the edge and the
beginning of the list of edges.
Dan
On Sep 16, 2008, at 2:58 PM, Prakash Prabhu wrote:
> Hi Dan,
>
> Thanks for the reply. I got the labels for each outgoing edge (at the
> source node's 'structure' field) working. Is
2012 Jun 02
0
[LLVMdev] DFG of machine functions
I tried debugging it and the issue seems to be in the implementation of
MachineInstrIterator.h and the way it interacts with GraphWriter.h
functions. I found this by replacing the ( template <> struct
GraphTraits<MCDFGraph<MachineFunction*> >) with a similar MCDFGraph based
template of CFG similar to the one in MachineFunction.h (similarly
replacing the DOTGraphTraits with the
2012 May 31
2
[LLVMdev] DFG of machine functions
Hi,
I am trying to generate the DFG of machine functions.
Initially, I added a pass to generate the DFG of LLVM IR functions. This
was based on the mail thread -
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025582.html. This
pass worked fine and I was able to generate DFG of LLVM IR functions.
Later, I ported the DFG pass code for machine functions. I ported the
InstIterator.h
2002 Oct 28
2
[LLVMdev] Compile error in include/Support/GraphWriter.h
Bill? Wendling wrote:
>Also sprach Casey Carter:
>} Issue: GraphWriter includes <ostream>, which my gcc2 apparently thinks
>} is <ostream.h>.
>} Fix: Make a new <Support/ostream> that handles this discrepancy, ala
>} <Support/hash_set>.
>}
>Um...was it entirely necessary to issue *8* email messages to the group
>with mostly single-line fixes
2005 Feb 17
5
[LLVMdev] questions about installing llvm
Actually, Misha, that won't work.
The -C option is used directly in docs/Makefile. So the change will have
to go into docs/Makefile. Either that or upgrade install to version 5.
Reid.
On Thu, 2005-02-17 at 11:33, Misha Brukman wrote:
> On Thu, Feb 17, 2005 at 01:21:20PM -0600, Feng Chen wrote:
> > llvm[1]: Installing HTML documentation
> >
2004 Dec 21
3
[LLVMdev] Help with code
Constant *strcon==ConstantArray::get("Value : %d\n");
Sorry Typo.
On Tue, 21 Dec 2004, Misha Brukman wrote:
> On Tue, Dec 21, 2004 at 03:45:33PM -0700, Sriraman Tallam wrote:
> > I have this call instruction to printf inserted which is causing
> > an assertion failure. Any pointers to where I am wrong :
> >
> > Function
2004 Jun 23
3
[LLVMdev] weird issue with mem2reg
On Wed, Jun 23, 2004 at 03:50:09PM -0500, Patrick Meredith wrote:
> MetaSplit is an anlysis I just finished writing. It doesn't alter
> anything, all it does is build a set of "program instructions". For
> some reason even though if I run it with any other combination of
> passes I've found, anytime I run it with mem2reg I get a seg fault in
> dyn_cast!
2004 Oct 07
2
[LLVMdev] problem with lli (llvm 1.3)
Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" but
there was no output. Maybe this is the probelm, I do have
CXX = g++ -mcpu=v9
CC := gcc -mcpu=v9
in the Makefile.config. Do I need to add -m64 as well? Thanks.
Shukang
On Thu, 7 Oct 2004, Misha Brukman wrote:
> Is your compiler configured to define __sparcv9 when it compiles?
> The following should tell
2004 Aug 21
2
[LLVMdev] Can't get llvmg++ to work
On Fri, 20 Aug 2004 08:52:28 -0700
Reid Spencer <reid at x10sys.com> wrote:
> Hi Jeff,
>
> On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote:
> > OK. I've built the front end without any heartaches, but I did
> > encountered the following glitches:
> >
> > The documentation of --with-llvmgccdir is a bit ambiguous. I had to
> > try several paths
2005 Feb 17
0
[LLVMdev] questions about installing llvm
On Thu, Feb 17, 2005 at 11:39:27AM -0800, Reid Spencer wrote:
> Actually, Misha, that won't work.
Sorry, Reid, but I think it will, for the following reason:
I don't really know what the -c (lowercase) option does, but install
says it's ignored anyway, so that's irrelevant for GNU install. We're
talking about the -C option (uppercase).
> The -C option is used directly
2004 Jun 23
4
[LLVMdev] weird issue with mem2reg, should have guessed
On Wed, 23 Jun 2004, Patrick Meredith wrote:
> What's different about code that's been mem2reg'd from straight front end
> code, or anything that mem2reg hasn't been run on? PHINODES!
Yup, front-ends generally don't produce SSA form. :)
> It appears to be crashing when I try to cast a Value* that's really a
> BB* (from the PHInode operands) to a User*,
2004 Sep 24
0
[LLVMdev] Little win32/Signals.cpp patch
On Fri, Sep 24, 2004 at 09:38:44AM -0700, Jeff Cohen wrote:
> Here's the patch to Signals.cpp. assuming that stdio.h is acceptable
> (can't imagine it won't work).
We prefer #include <cstdio>, since this is C++ after all. :)
--
Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu
2004 Sep 24
3
[LLVMdev] Little win32/Signals.cpp patch
Here's the patch to Signals.cpp. assuming that stdio.h is acceptable
(can't imagine it won't work).
On Fri, 24 Sep 2004 09:29:05 -0700
Jeff Cohen <jeffc at jolt-lang.org> wrote:
> Uh... this may be a silly question, but why can't you include <stdio.h>?
> It'd be much better than <iostream>.
>
> Anyway, I think I'll try this weekend to come
2004 Sep 03
2
[LLVMdev] diffs for vc7.1
On Fri, Sep 03, 2004 at 03:01:01PM -0500, Anshu Dasgupta wrote:
> ><snip>
> >for (BasicBlock::iterator I = Dest->begin(); PHINode *PN =
> >dyn_cast<PHINode>(I); ++I)
> > visitPHINode(*PN);
> ><snip>
> >
> >build_vc71\lib\Transforms\Scalar\SCCP.cpp(202) : error C2275:
> >'llvm::PHINode' : illegal use of this type as
2004 Oct 20
5
[LLVMdev] Re: LLVM Compiler Infrastructure Tutorial
I'm CC'ing the llvm-dev list because other people are more knowledgeable
about the bytecode format/encoding than I am. Please follow-up the
replies to the list.
On Wed, Oct 20, 2004 at 11:27:53AM -0700, Yiping Fan wrote:
> We also want to extend the llvm instructions/intrinsic
> functions/types/passes to support our high-level synthesis for
> hardware. First of all, we want to