Displaying 20 results from an estimated 11000 matches similar to: "[LLVMdev] Simplifying C++ template error messages"
2009 Aug 25
0
[LLVMdev] Simplifying a front-end project
On Tue, Aug 25, 2009 at 3:01 PM, Vikram S. Adve<vadve at cs.uiuc.edu> wrote:
> For my introductory Compiler Construction class, I have been giving
> the students a project to write a simple compiler for a toy, single-
> inheritance object-oriented language. We give them a set of classes
> implementing an AST for the language and a type checker as well. The
> students write
2005 Sep 05
1
[LLVMdev] dependence analyzer for machine code?
On Sep 5, 2005, at 10:21 AM, Andrew Lenharth wrote:
> On Mon, 2005-09-05 at 14:45 +0800, Tzu-Chien Chiu wrote:
>
>> why there is no general dependency analysis for the "machin code"?
>> perhaps it's because the instruction scheduling is only implemented
>> for sparcv9?
>>
>
> Most backends use the SelectionDAG infastructure to do this kind of
>
2009 Aug 25
4
[LLVMdev] Simplifying a front-end project
For my introductory Compiler Construction class, I have been giving
the students a project to write a simple compiler for a toy, single-
inheritance object-oriented language. We give them a set of classes
implementing an AST for the language and a type checker as well. The
students write (1) a scanner and parser to build the AST; (2) a
translator from AST to LLVM; and (3) a couple of
2003 Oct 23
0
[LLVMdev] RE: Ticket #7559: FW: Bradfields/PCJF-10959
Sorry for that last message, it was intended for llvm at cs instead of
llvmdev at cs.
--Vikram
http://www.cs.uiuc.edu/~vadve
> -----Original Message-----
> From: Vikram S. Adve [mailto:vadve at cs.uiuc.edu]
> Sent: Thursday, October 23, 2003 1:55 PM
> To: 'Nate Fyie'
> Cc: 'LLVM Developers List'
> Subject: RE: Ticket #7559: FW: Bradfields/PCJF-10959
>
>
2003 Oct 23
0
[LLVMdev] RE: Ticket #7559: FW: Bradfields/PCJF-10959
Great! Could you please add a /localhome directory to each of them?
Since there are 2 disks per machine, perhaps the best thing to do would
to make /localhome a real directory and make separate local directories
on each disk, so that we can each do something like this:
/localhome/vadve -> /mounts/seraph/disks/0/localhome/vadve
/localhome/lattner ->
2003 Sep 25
0
FW: [LLVMdev] basic block tracing
Rahul,
Were you talking about tracing in the sense of "profiling" (which Anand
did), or tracing of values as they are computed for debugging generated
code (which I did)?
For tracing of values for debugging, the answer is yes: we insert code
in each BB and print out the values computed in that BB that are live at
the end of the BB (so we don't print out temporaries computed and
2009 Oct 19
0
[LLVMdev] [cfe-dev] Developer meeting videos up
I too am disappointed that not all talk slides are posted. To me it speaks
poorly of the whole meeting since there were parallel sessions and not
everyone could attend in person all the sessions they wanted to. The slides
are, I thought, meant to be like the "proceedings" and If I recall some of
the Apple slides are present from previous years but not this year.
Vinod
On Sat, Oct 17,
2009 Jul 11
0
[LLVMdev] ANTLR?
When you create a parser via ANTLR you specify the output language of the
resulting recursive descent parser, at the moment there exists no C++ output
template to my knowledge, thus you would have to generate the parser as C
code for which a template exists.
The runtime support should be there, at least partially but it won't use
things like exceptions, nor will it have a very modular design
2002 Oct 31
1
[LLVMdev] problems with llvmgcc
Dear Prof. Adve,
Now I can use llvmgcc to compile a .c file into .bc file. But I still have
trouble simply run the .bc code. Below is the sequence I got when I tried.
I really don't know what's going on here. Please let me know how can I fix
it.
Thanks,
xiaodong
xli3|csil-suna48|~/cs426|[13]% llvmgcc scalarize.c -o scalarize
xli3|csil-suna48|~/cs426|[14]% scalarize
Cannot load value of
2005 May 23
1
[LLVMdev] Sparc build error
I'm encountering a new problem building llvm (from CVS) on Solaris.
The tblgen executable builds successfully but it seems to use the
wrong version of libstdc++ :
% /home/vadve/vadve/llvm-sparc/Debug/bin/tblgen --help
ld.so.1: /home/vadve/vadve/llvm-sparc/Debug/bin/tblgen: fatal: /home/
vadve/lattner/local/x86-fc1/gcc-3.4.2/lib/libstdc++.so.6: wrong ELF
class: ELFCLASS32
Killed
This
2007 Jun 08
1
[LLVMdev] Fwd: PC Magazine
Our department outreach coordinator spotted this and forwarded it to
me. It's a lot of speculation but I thought many of you would be
interested.
--Vikram
http://www.cs.uiuc.edu/~vadve
http://llvm.org
Begin forwarded message:
> From: "Jennifer C La Montagne" <jsandone at uiuc.edu>
> Date: June 8, 2007 12:53:00 PM CDT
> To: "Vikram Sadanand Adve"
2006 Mar 15
1
[LLVMdev] Inline hints for *compiler clients*
On Mar 15, 2006, at 3:27 PM, John Criswell wrote:
> Vikram S. Adve wrote:
>
> Hmmm. It seems the discussion has grown a little bit larger than I
> had intended.
> :)
>
> Basically what I think would be useful is an option to the inliner
> that gives it a list of functions to skip when inlining. My
> argument for this is that we have several transformations now
2002 Nov 12
0
[LLVMdev] (no subject)
P.S. If anyone can take a little time to write a GraphTraits class for
the call graph, using the call sites returned by the TDGraph, that would
be great.
Then you could directly use the PostOrderIterator,
ReversePostOrderIterator, and TarjanSCCIterator on this call graph,
without having to do any extra work. You can also do other things like
print out the call graph to dot files and view them.
2017 Feb 01
0
[RFC] IR-level Region Annotations
> On Jan 31, 2017, at 7:53 PM, Tian, Xinmin <xinmin.tian at intel.com> wrote:
>
> In this case, inliner is educated to add all local variables to the tag of enclosing parallel region, if there is enclosing parallel region.
So isn’t it a good example that shows that your intrinsic *cannot* be opaque and that IR passes need to be modified to handle not only the IR-region
2006 Apr 26
5
[LLVMdev] Re: Newbie questions
On Apr 26, 2006, at 10:45 AM, Tom Tromey wrote:
>>>>>> "Vikram" == Vikram Adve <vadve at cs.uiuc.edu> writes:
>
> Vikram> Either way, one issue that you will have to deal with is
> preserving
> Vikram> the behavior of Java exceptions (assuming you care about
> that). LLVM
> Vikram> does not preserve the order of potentially
2017 Feb 01
2
[RFC] IR-level Region Annotations
> On Jan 31, 2017, at 10:59 PM, Tian, Xinmin <xinmin.tian at intel.com> wrote:
>
>
> <>
> From: mehdi.amini at apple.com <mailto:mehdi.amini at apple.com> [mailto:mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>]
> Sent: Tuesday, January 31, 2017 9:03 PM
> To: Tian, Xinmin <xinmin.tian at intel.com <mailto:xinmin.tian at
2008 Apr 11
0
[LLVMdev] choice between SSAPRE and bitvector aporach
On Apr 4, 2008, at 8:28 PM, Daniel Berlin wrote:
> On Fri, Apr 4, 2008 at 5:58 PM, Vikram S. Adve <vadve at cs.uiuc.edu>
> wrote:
>>
>>
>> Dan,
>>
>> Doesn't the paper also assume the invariant that phi operands are
>> effectively dead after the Phi, which is true right after SSA is
>> constructed, but potentially not after
2017 Feb 01
0
[RFC] IR-level Region Annotations
Sent from my iPhone
> On Jan 31, 2017, at 7:27 PM, Tian, Xinmin <xinmin.tian at intel.com> wrote:
>
> Remember that, the prepare-phase is invoked in the FE or right after FE, inlining is not happening, that is why we don't call it "pass". Chandler made a good point for this case a long time back.
>
What I was describing is the inlining in the optimizer
2009 Jul 11
2
[LLVMdev] ANTLR?
That sounds like a problem. Just so I understand, do you mean there
isn't the run-time support etc. to write back ends for the C++
language, or that the compiler IR is also somehow insufficient to
write a code generator?
--Vikram
Associate Professor, Computer Science
University of Illinois at Urbana-Champaign
http://llvm.org/~vadve
On Jul 11, 2009, at 3:00 PM, Granville Barnett
2002 Sep 18
0
[LLVMdev] RE: Disk Space on /usr/dcs/projects
Thanks for the warning! I checked and the executables take up about 2/3 of
the space (380MB) vs. about 180MB for the libs. Since we are usually only
debugging one executable at a time (if any), I modified Makefile.common to
strip each executable in tools/Debug by default. You can define
KEEP_SYMBOLS in the Makefile of any particular tool in order to avoid
stripping that executable.
I have