Displaying 10 results from an estimated 10 matches for "brethour".
2004 May 13
0
[LLVMdev] new project: LLVM-TV
...n of LLVM. Or, if you don't want
to go to the trouble of building it, you can read the user's guide,
which has many pretty screenshots!
Visit our project's web-site at: http://llvm.cs.uiuc.edu/~gaeke/llvm-tv
Our abstract is attached.
Thanks,
-Brian Gaeke, Misha Brukman & Tanya Brethour
------------------------------------------------------------------------------
CS497rej: Object-Oriented Programming and Design (Spring 2004)
LLVM Visualization Tool
Misha Brukman, Tanya Brethour, and Brian Gaeke
The LLVM Visualization Tool (LLVM-TV) can be used to visualize the effects of
tran...
2003 Nov 24
1
[LLVMdev] Question about Instruction comparison
On Mon, Nov 24, 2003 at 02:13:04PM -0600, Tanya Brethour wrote:
> > I have been looking over the doxygen documentation as well as the
> > llvm code. Is there a standard way to check to see if two
> > instructions are identical (i.e., Inst1 == Inst2 does not work)?
>
> If you want to check if two instructions are the same instruc...
2002 Sep 18
0
[LLVMdev] RE: Disk Space on /usr/dcs/projects
...: (217) 244-2016
Univ. of Illinois at Urbana-Champaign FAX: (217) 244-6869
1304 W. Springfield Ave. http://www.cs.uiuc.edu/~vadve
Urbana IL 61801.
----------------------------------------------------------------------
> -----Original Message-----
> From: Tanya Brethour [mailto:tonic at nondot.org]
> Sent: Tuesday, September 17, 2002 10:46 PM
> To: Vikram Adve
> Subject: Disk Space on /usr/dcs/projects
>
>
>
> I heard a little rumour that the disk /usr/dcs/projects was reaching
> capacity. So I took a look and its around 94%. Considering I...
2003 Nov 24
2
[LLVMdev] Question about Instruction comparison
I have been looking over the doxygen documentation as well as the llvm
code. Is there a standard way to check to see if two instructions are
identical (i.e., Inst1 == Inst2 does not work)?
Thanks,
Brian
Brian M. Fahs
Graduate Student
University of Illinois
2003 Nov 24
0
[LLVMdev] Question about Instruction comparison
> I have been looking over the doxygen documentation as well as the llvm
> code. Is there a standard way to check to see if two instructions are
> identical (i.e., Inst1 == Inst2 does not work)?
If you want to check if two instructions are the same instruction, you
should be able to just compare pointers.
-Tanya
2004 Aug 03
0
[LLVMdev] Compiler Driver Decisions
> > > Since there's been little feedback on the design document I sent out,
> > > some decisions are being made in order to progress the work. If you have
> > > strong feelings about any of these, voice them now!
> > >
> > > 1. Name = llvmcc
> >
> > Why not 'llvmc' "llvm compiler"? What does the extra C mean?
>
>
2004 Aug 03
1
[LLVMdev] Compiler Driver Decisions
> On Mon, 2 Aug 2004, Reid Spencer wrote:
> > I actually like Misha's point here. Most people that have used GCC
> > recently realize that the CC means "Compiler Collection" and not "C
> > Compiler" which is appropriate given what it does. Since we intend to be
> > front end language agnostic and the driver tool will support multiple
> >
2003 Nov 14
1
[LLVMdev] Headers & Libraries
On Fri, 2003-11-14 at 11:49, Alkis Evlogimenos wrote:
> On Friday 14 November 2003 01:22 pm, Reid Spencer wrote:
> > There is no separation of headers and cpp files. When I specify my
> > makefiles, I indicate which headers are public (installable) and which
> > are private (not installed).
>
> IMO it is better to include with "" internal header files that are
2004 Aug 03
4
[LLVMdev] Compiler Driver Decisions
On Mon, 2004-08-02 at 15:03, Chris Lattner wrote:
> > Since there's been little feedback on the design document I sent out,
> > some decisions are being made in order to progress the work. If you have
> > strong feelings about any of these, voice them now!
> >
> > 1. Name = llvmcc
>
> Why not 'llvmc' "llvm compiler"? What does the extra C
2003 May 21
0
[LLVMdev] Bug submission instructions
Ever thought of using something like bugzilla?
-Tanya
On Wed, 21 May 2003, Chris Lattner wrote:
>
> FYI: I just posted a short document with instructions on how to submit a
> proper bug report. If you run into problems using LLVM, please let us
> know. The instructions indicate steps to properly narrow down the bug,
> which will make life easier for the bug-fixer. :)
>
>