Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] A. Pool Allocation under PowerPC (Mac)"
2005 May 27
0
[LLVMdev] A. Pool Allocation under PowerPC (Mac)
Ricardo wrote:
> Hello,
>
> Is PA working on the macintosh already?
Although we may not have run it on MacOS X recently, I believe that it
should work. We've run it on several architectures and operating
systems, including SparcV9/Solaris.
If you find that PA doesn't compile or work on MacOS X, please file a
bug report (http://llvm.cs.uiuc.edu/bugs/) so that we can fix it.
2005 May 27
2
[LLVMdev] A. Pool Allocation under PowerPC (Mac)
John,
Thanks for the information. That comment in the source code confused me and I wanted to be sure
that the installation of all the LLVM framework in the macintosh for testing the pool allocation
was not going to be done in vain.
The LLVM documentation states that gcc 3.4x is necessary for compiling the LLVM. On the other
hand, Xtools 1.5 for Mac includes only gcc 3.3 and Xtools 2.0 includes
2001 Apr 28
1
R 1.2.3 for MacOS/X available
From release 1.2.3, R can run different Macintosh platforms.
Two versions are currently available that are non concurrent.
One version runs on MacOS Systems from 8.6 to 9.1 and MacOSX using the
standard MacOS/MacOSX interface, that means that is behaves like any
usual Macintosh application. (This is mantained by Stefano M. Iacus)
The other version is a Darwin/X11 that means a Unix-like
2007 Jan 24
2
[LLVMdev] llvm-poolalloc compilation failed
I tried to compile the currently checked in version of llvm-poolalloc
with the curently checked in version of llvm and got the following errors:
llvm[4]: Compiling Heuristic.cpp for Debug build (PIC)
Heuristic.cpp: In function 'bool Wants8ByteAlignment(const llvm::Type*,
unsigned int, const llvm::TargetData&)':
Heuristic.cpp:77: error: 'const class llvm::TargetData' has no
2001 Nov 19
3
installation on Mac OS X
Help ! I am a graduate student in statistics, nearing the end of my
first semester, and recently discovered R, but cannot figure out how to
install it on my Mac. I am currently running OS 10.1.1, and know next
to nothing about Unix or anything related. I would like to install this
program on my Powerbook, as it come highly recommended, so I can use it
for a class next semester. Any help
2007 Jan 24
0
[LLVMdev] llvm-poolalloc compilation failed
On Tue, 23 Jan 2007, Ryan M. Lefever wrote:
> I tried to compile the currently checked in version of llvm-poolalloc
> with the curently checked in version of llvm and got the following errors:
>
> llvm[4]: Compiling Heuristic.cpp for Debug build (PIC)
> Heuristic.cpp: In function 'bool Wants8ByteAlignment(const llvm::Type*,
> unsigned int, const llvm::TargetData&)':
2007 Jan 24
3
[LLVMdev] llvm-poolalloc compilation failed
This kind of regression is a fallout of having some code live in
separate CVS modules as "projects." It would help to have someone
volunteer to maintain each project, which can be as little as making
sure it continues to compile or as much as supporting it with answers
to questions and bug fixes. Here is the current list of projects:
llvm-poolalloc
llvm-java (currently unused
2005 May 12
2
[LLVMdev] Current Regressions
Dear All,
Here is a more complete list of regressions for the platforms listed
below. Some of the regressions from the previous list I emailed a few
days ago have been fixed or were false positives. Thanks to all who've
helped fix things.
We would like to try to get as many of these fixed as possible before I
create the release branch (still scheduled for tomorrow, Friday).
I'll
2004 Sep 29
4
[LLVMdev] LLVM build error (sparc gcc 3.2.2)
Hi,
I met some errors when I tried to build LLVM. The tar file is
llvm-1.3.tar.gz. I am using a sparc machine with gcc 3.2.2.
-------------
Compiling SparcV9CodeEmitter.cpp
/uf24/zhou/research/llvm/src/lib/Target/SparcV9/SparcV9CodeEmitter.cpp: In
static member function `static void
llvm::<unnamed>::JITResolver::CompilationCallback()':
2007 Jan 24
0
[LLVMdev] llvm-poolalloc compilation failed
Vikram S. Adve wrote:
> This kind of regression is a fallout of having some code live in
> separate CVS modules as "projects." It would help to have someone
> volunteer to maintain each project, which can be as little as making
> sure it continues to compile or as much as supporting it with answers
> to questions and bug fixes. Here is the current list of projects:
2008 Jun 16
6
[LLVMdev] PowerPC instruction cache invalidation
Hi all,
When you genetate code on PowerPC you need to explicitly invalidate
the instruction cache to force the processor to reread it. In LLVM
there is code to do this for function stubs on Macintosh, but not
for other platforms and not for JITted code generally.
The attached patch adds support for GNU platforms, but I can't figure
out a nice way to call it for all generated code. Can
2005 May 13
0
[LLVMdev] Current Regressions
On Thu, 12 May 2005, John Criswell wrote:
> Here is a more complete list of regressions for the platforms listed below.
> Some of the regressions from the previous list I emailed a few days ago have
> been fixed or were false positives. Thanks to all who've helped fix things.
>
> We would like to try to get as many of these fixed as possible before I
> create the release
2007 Feb 06
1
[LLVMdev] llvm-poolalloc compilation failed
Chris,
I performed the steps you gave below to check out llvm-poolalloc. When
I want to get new updates made to llvm-poolalloc, do I perform the
following commands?
cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login
<Hit return for an empty password>
cd llvm/projects
cvs -d :pserver:anon at llvm.org:/var/cvs/llvm update -r release_19
llvm-poolalloc
In other words, do I specify the
2005 Jun 17
5
[LLVMdev] Re: Control flow graph
On Fri, 17 Jun 2005, Manvi Agarwal wrote:
> Hi Chris,
Hi. FYI, it's usually better to email the llvmdev list with generic llvm
questions.
> Is it possible to get control flow graph of the application with the llvm
> infrastructure in terms of basic blocks?
Yes, given a BasicBlock*, you can iterate over the pred/succ blocks in the
CFG like this:
#include
2008 Jun 16
0
[LLVMdev] PowerPC instruction cache invalidation
Hi Gary,
Gary Benson wrote:
> Hi all,
>
> When you genetate code on PowerPC you need to explicitly invalidate
> the instruction cache to force the processor to reread it. In LLVM
> there is code to do this for function stubs on Macintosh, but not
> for other platforms and not for JITted code generally.
>
>
Did you run into errors when not invalidating the cache? vmkit
2005 Jun 28
3
[LLVMdev] LLVM 1.5 C Front-End Binaries for FreeBSD?
Might anyone have a FreeBSD binary or suggested modifications to the
source to compile one?
Thanks,
Sean
2004 Jan 07
2
[LLVMdev] Services Restored
Dear LLVM Developers,
The LLVM website, CVS repository, and SAFECode website should now be back
online.
Should you encounter any problems with the LLVM services, please send email to
llvmdev at cs.uiuc.edu so that we may fix it.
Regards,
John T. Criswell
*********************************************************************
* John T. Criswell Email: criswell at uiuc.edu
2007 Dec 17
3
[LLVMdev] Bug 1868: Specifying Pass Orderings
Dear Devang Patel,
In response to your comment on bug 1868, how do I get BottomPass to
requires Pass2 before Pass1? Is it by reversing the order of the calls
to AU.addRequired()?
-- John T.
--
John T. Criswell
jcriswel at bigw.org
"It's today!" said Piglet. "My favorite day," said Pooh.
2005 Nov 01
4
[LLVMdev] LLVM Release Branch
Dear All,
Do people think that they are ready to create the LLVM 1.6 release
branch? I believe all the development is pretty much done.
Is all the documentation in the LLVM source tree updated and ready? I'm
not able to make a full doc review like I've been able to do in previous
releases, so I need volunteers to work on the docs if they're not done
yet.
-- John T.
--
John
2008 Jun 16
0
[LLVMdev] PowerPC instruction cache invalidation
On Mon, 16 Jun 2008, Gary Benson wrote:
> When you genetate code on PowerPC you need to explicitly invalidate
> the instruction cache to force the processor to reread it. In LLVM
> there is code to do this for function stubs on Macintosh, but not
> for other platforms and not for JITted code generally.
Applied, thanks!