Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] aid for getting started"
2008 Apr 23
1
[LLVMdev] getting closer!
On Apr 22, 2008, at 5:43 PM, Gordon Henriksen wrote:
> This is not possible for instructions (which must be in SSA form). You
> can only use it for constants.
>
> http://llvm.org/docs/LangRef.html#constantexprs
ah! ok, but really helpful for structs init. cool.
>> I'm always using the pure text input headline generating everything
>> from Java...
>
> Normally
2008 Apr 24
0
[LLVMdev] templates vs code to generate IR
Hi Terence,
The reason I remarked, actually, is that for LLVM in particular the C+
+ API offers more safety, and emitting .ll generally requires at least
partially reimplementing the IR object model. I think this is a topic
in the FAQ. But both are perfectly valid approaches!
- Gordon
On Apr 23, 2008, at 14:04, Terence Parr <parrt at cs.usfca.edu> wrote:
> Gordon reminded me that
2008 Apr 23
2
[LLVMdev] templates vs code to generate IR
Gordon reminded me that most people seem to generate code using code,
whereas it has become natural for me to use templates to generate
code. Let me include an example from an article I'm working on (Java
centric). The same argument goes for LLVM IR templates versus using
the C++ interface. Generating LLVM IR for me is super simple. Here
are a few of my templates for generating IR
2007 Aug 21
0
[LLVMdev] Problems building llvm-gcc-4.2 on ppc32, OS X 10.4.10
Hi, I'm guessing that no one has tried this exact combination yet.
I'm trying to build the gcc4.2 front end with current LLVM SVN
on a G4 Powerbook running 10.4.10.
I started with this:
../gcc4.2-trunk/configure
--prefix=$HOME/Documents/hpcl/LLVM/llvm-gcc-4-2/install
--enable-llvm=$HOME/Documents/hpcl/LLVM/llvm-svn-obj/
--with-gmp=$HOME/Documents/hpcl/LLVM/llvm-gcc-4-2/libdeps
2008 Apr 23
2
[LLVMdev] getting closer!
On Apr 22, 2008, at 3:27 PM, Gordon Henriksen wrote:
> If you'd like to propose clarified language once you've wrapped your
> head around the framework, I'd be happy to incorporate it. Most
> ideally, submit a patch against GarbageCollection.html in http://llvm.org/svn/llvm-project/llvm/trunk/docs/
> .
Cool. Ok, I have already submitted some svn diffs to Chris to fix
2008 Apr 23
0
[LLVMdev] getting closer!
On Apr 22, 2008, at 20:19, Terence Parr wrote:
> On Apr 22, 2008, at 3:27 PM, Gordon Henriksen wrote:
>
>>> 1. How do I know the offset (due to alignment/padding by LLVM) of
>>> a pointer within an object using {...} struct type? GEP
>>> instruction gets an address, of course, but how does my C
>>> collector compute these. Do I need to make a
2008 Apr 22
3
[LLVMdev] getting closer!
Ok, I *might* be getting this from the assembly code. The assembly
code has:
L_llvm_gc_root_chain$non_lazy_ptr:
.indirect_symbol _llvm_gc_root_chain
.long 0
and I see it being used in the function preamble. Is that a ref to an
extern symbol or the def? I.e., is it referring to
StackEntry *llvm_gc_root_chain;
that I must have in my GC C code? (semispace.c has it)
SO!
2008 Apr 21
2
[LLVMdev] getting started with IR needing GC
On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote:
> The shadow stack walker is in the runtime directory with the semispace
> heap example. The runtime directory is built to LLVM IR using llvm-
> gcc. So it's skipped unless you configure llvm with llvm-gcc support.
doh! That's how I missed the binary. thanks!
> Since the semispace heap doesn't actually work (it's
2008 Apr 22
2
[LLVMdev] getting closer!
On Apr 21, 2008, at 6:23 PM, Gordon Henriksen wrote:
> On Apr 21, 2008, at 20:09, Terence Parr wrote:
>
>> Ok, I *might* be getting this from the assembly code. ... From
>> that, it will push/pop in functions? If so, that's easy enough. :)
>
> Yup! Sounds like you've got it.
Yup, what i was missing and what somebody should add to the doc is
that
2008 Apr 21
2
[LLVMdev] getting started with IR needing GC
On Apr 20, 2008, at 6:52 PM, Gordon Henriksen wrote:
> On 2008-04-20, at 21:05, Terence Parr wrote:
>
>> On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote:
>>
>>> Since the semispace heap doesn't actually work (it's an example,
>>> at best), I suggest you simply copy the stack visitor into your
>>> project; it's only a dozen lines of
2008 Apr 21
0
[LLVMdev] getting started with IR needing GC
Hi Terence,
On 2008-04-20, at 20:08, Terence Parr wrote:
> I've exhausted what I can do on my own to make a GC example bind
> (usual googling, reading, playing, looking at source). I can't find
> the shadow collector lib or perhaps the -l options needed to link my
> sample (not even to point where I'm figuring out GC actually as I
> can't link).
The shadow
2008 Apr 21
0
[LLVMdev] getting started with IR needing GC
On 2008-04-20, at 21:05, Terence Parr wrote:
> On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote:
>
>> Since the semispace heap doesn't actually work (it's an example, at
>> best), I suggest you simply copy the stack visitor into your
>> project; it's only a dozen lines of code or so.
>
>
> Ok, copying; can't find ShadowStackEntry though.
2008 Apr 21
2
[LLVMdev] getting started with IR needing GC
Howdy do LLVM folks!
I've exhausted what I can do on my own to make a GC example bind
(usual googling, reading, playing, looking at source). I can't find
the shadow collector lib or perhaps the -l options needed to link my
sample (not even to point where I'm figuring out GC actually as I
can't link). Not sure this IR is correct but here is what I've been
playing
2008 Apr 25
1
[LLVMdev] Question about Doc patch
On Apr 25, 2008, at 14:32, Terence Parr wrote:
> Howdy. I submitted a number of documentation patches to Chris, but
> he wanted your input on this one:
>
>>> Also, is this correct:
>>>
>>> %class.Array = type { %class.Object, i32, [0 x %class.Object*] }
>>> ? Wondering if it should be
>>> %class.Array = type { %class.Object*, i32, [0 x
2008 Feb 10
0
[LLVMdev] semicolon breaking builds on llvm-gcc4.2 cygwin build for arm target 2.2prerelease2
Since we are fast approaching the 10th, I thought it appropriate to report
this "bug" with the build despite not having worked around it.
Build environment is
*Summary:*
When building llvm-gcc with a arm-apple-darwin target on i686-pc-cygwin,
make fails because child calls to configure have an errant semicolon that
causes the --srcdir parameter to be ignored by the configure script.
2013 Apr 19
2
R 3.0, Rtools3.0,l Windows7 64-bit, and permission agony
Having finally found some free time, I was going to use it to update a
bunch of R packages from 2.15 to 3.0.
I am running Windows 7, 64-bit professional. This is on a brand-new
laptop using vanilla settings when installing the operating system.
Problem 1: I installed R3.0 to the default location (C:\Program
FIles\R\R-3.0.0). The first thing I tried to do was install
BioConductor. This
2007 Apr 01
3
[LLVMdev] trouble compiling llvm-gcc4 1.9
I'm having some trouble getting llvm-gcc4 to compile. It's unable to
compile darwin-crt3.c. It's mentioning "Complex expression. Absolute
segment assumed." but I'm not sure if that's a real error message. Has
anyone run into this before? I'm running on a G4 apple 10.4.8, kernel
version 8.6.0. I googled around and found a bug with the same error message:
2011 Dec 16
0
[LLVMdev] llvm/clang test failures on powerpc-darwin8
On Fri, Dec 16, 2011 at 12:17:32PM -0500, David Fang wrote:
>>> These results have far fewer failures than svn-trunk, and are also
>>> comparable to bootstrapping with gcc-4.6.2, summarized here:
>>> http://paste.lisp.org/display/126363
>>> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.)
>>> This consistency between
2011 Dec 16
0
[LLVMdev] llvm/clang test failures on powerpc-darwin8
On Fri, Dec 16, 2011 at 01:51:57AM -0500, David Fang wrote:
> Hi,
> Thanks for the quick reply again.
>
>> On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote:
>>> Hi,
>>>
>>> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and
>>> have the following test results to share.
>>>
2007 Sep 19
2
[LLVMdev] Building current llvm-gcc-4.0 TOT fails on darwin x86
Hi all,
building current llvm-gcc-4.0 TOT(Revision: 42128) with current llvm
(Revision: 42128) on 8.10.1 Darwin (x86) fails with the following
message. Is that a just a temporary inconsistency or should i file a
bug?
/Users/arnold/Desktop/testing/vanilla-gcc-4.0/obj/gcc/xgcc -B/Users/
arnold/Desktop/testing/vanilla-gcc-4.0/obj/gcc/ -B/Users/arnold/