Displaying 20 results from an estimated 8000 matches similar to: "[LLVMdev] building Kaleidoscope in xcode"
2017 Sep 20
6
[Bug 13044] New: On macOS 10.12.6 with the new Xcode 9, `make check` is full of failures
https://bugzilla.samba.org/show_bug.cgi?id=13044
Bug ID: 13044
Summary: On macOS 10.12.6 with the new Xcode 9, `make check` is
full of failures
Product: rsync
Version: 3.1.2
Hardware: x86
OS: Mac OS X
Status: NEW
Severity: regression
Priority: P5
Component: core
2012 Dec 15
0
[LLVMdev] Kaleidoscope Build Problems - (OCaml)
Hello everyone...
I'm hoping that someone can give me insight as to why I am having problems
building the Kaleidoscope example for OCaml.
Platform: Mac OS 10.8.2
OCaml version: 4.00.1
LLVM version: 3.1
XCode version: 4.5.2
I successfully build the examples when running "gnumake BUILD_EXAMPLES=1"
in the OBJ_DIR, however when I try to build them from outside the build
tree (ie move
2011 Jun 11
0
[LLVMdev] Kaleidoscope Build Error
(cc'ing llvm-dev)
Hello Gregory,
i just recompiled llvm from scratch, and was able to build the ocaml
kaleidoscope bindings. Did you know the llvm's build system already
can compile the kaleidoscope tutorials for you? You can run this to
build them:
make BUILD_EXAMPLES=1
Or just cd into the examples directory in your build directory, and
run "make" there.
Anyway, I think the
2016 Aug 29
2
cmake configuration changes to build Kaleidoscope outside of llvm examples src tree
I try to understand cmake build configuration. As an example, I copied
Kaleidoscope from llvm examples to some other directory (e.g.,
/tmp/Kaleidoscope). What change(s) that I need to make to "CMakkeLists.txt"
in order to build Kaleidoscope from /tmp/Kaleidoscope?
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2013 Jun 04
1
[LLVMdev] MCJIT and Kaleidoscope Tutorial
Hi Andrew,
Am 04.06.2013 02:13, schrieb Kaylor, Andrew:
> Hi Dmitri,
>
> You might want to try replacing the call to JMM->invalidInstructionCache() with a call to TheExecutionEngine->finalizeObject(). If you are getting a non-NULL pointer from getPointerToFunction but it crashes when you try to call it, that is most likely because the memory for the generated code has not been
2016 Apr 01
0
Kaleidoscope on Windows - bug maybe found?
Addendum: this still fails:
auto ExprSymbol = J.findSymbol("putchard");
As yet, I have no idea why - that symbol even seemed to be exported:
extern "C"
double putchard(double X) {
putchar((char)X);
return 0;
}
On Fri, Apr 1, 2016 at 2:42 AM, Russell Wallace <russell.wallace at gmail.com>
wrote:
> To try to find out why it was crashing, I followed the
2015 Jan 16
3
[LLVMdev] Function calls only being JIT'd once by Kaleidoscope with MCJIT?
Cheers Lang!
You were right, I was testing this on Linux.
I was planning on committing these changes with the corresponding
changes to the Kaleidoscope tutorial walk-through. Might be a bit of a
surprise to have no explanation of what MCJITHelper and friends is
doing.
I'll try and make time to prepare some patches along these lines, as
well as updating future chapters with the same fix.
2013 Jun 04
0
[LLVMdev] MCJIT and Kaleidoscope Tutorial
Hi Dmitri,
You might want to try replacing the call to JMM->invalidInstructionCache() with a call to TheExecutionEngine->finalizeObject(). If you are getting a non-NULL pointer from getPointerToFunction but it crashes when you try to call it, that is most likely because the memory for the generated code has not been marked as executable. That happens inside finalizeObject, which also
2010 Aug 17
2
multcomp issues on MAC OSX 10.6.4
Dear R-help list.I'm not big on programming, but I have a weird error on a couple of packages when trying to install them. I hope someone could help me :-).System: MacBook Pro (1.0) with OS X 10.6.4
R: Installed from web binaries: R version 2.11.1 (2010-05-31)
> Sys.getlocale()
[1] "en_GB.UTF-8/en_GB.UTF-8/C/C/en_GB.UTF-8/en_GB.UTF-8" I have been trying all day to install the
2014 Dec 26
2
[LLVMdev] Function calls only being JIT'd once by Kaleidoscope with MCJIT?
Hi all,
Starting from Chapter 4 of the Kaleidoscope tutorial (where the JIT
support is added), there's some strange behaviour,
ready> def foo(x y) x+y;
ready> Read function definition:
define double @foo(double %x, double %y) {
entry:
%addtmp = fadd double %x, %y
ret double %addtmp
}
ready> foo(1, 2);
ready> Evaluated to 3.000000
ready> foo(3, 4);
ready> Evaluated to
2010 Aug 13
0
[LLVMdev] Kaleidoscope example control flow to c like control flow?
Can anyone point me in the right direction so i can have c like control flow
in the Kaleidoscope example.
for example in Kaleidoscope it's
if a < 5 then
//do something;
to
if (a < 5)
{
//do something
}
im trying to use LLVM to create an audio signal processing library/code for
my music application to create music synths and audio effects.
Thanks.
--
View this message in
2010 Nov 16
2
[LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example)
Hi Dan,
The tutorial in r119335 does not build : the basicAA pass creation needs to be declared. This is addressed with the 'missing-include' patch, which updates both source code & documentation.
The second point is that beside basicAA, to get the optimizations as shown in the tutorial, (sin(x)*sin(x) -> sin(x)^2), some attributes need to be set on 'sin'. Patch
2012 Apr 01
1
Installing Wine with Xcode 4.3
Downloaded Xcode 4.3 for Lion from the app store, and am following the tutorial for installing wine:
http://www.davidbaumgold.com/tutorials/wine-mac/
When I get to part 3 and it tells me to type the following code into terminal
Code:
$ sudo port install wine
I get the following message:
Code:
xxx-xxx-macbook-pro:~ Kaoss$ sudo port install wine
Password:
Warning: xcodebuild exists but
2010 Jan 31
0
[LLVMdev] Compiling Kaleidoscope on Windows
Thanks to OvermindDL1 for pointing this out: compiling with Visual C++
actually works! Basically it's just a matter of running cmake (default
settings are fine) then nmake, and I've got what appears to be a
working version of LLVM.
Kaleidoscope crashes on attempting to exit with ^Z:
C:\llvm\bin>Kaleidoscope.exe
ready> 1+2;
ready> Evaluated to 3.000000
ready> 3*4;
ready>
2015 Feb 10
2
[LLVMdev] Some basic questions regarding MCJIT and Kaleidoscope sample
HI Dibyendu,
A single MCJIT instance can notionally manage multiple modules, but there
are caveats (which I'm afraid I don't remember off the top of my head) that
make it unattractive in practice. I believe most clients opt for something
like the ExecutionEngine-per-Module model used in the Kaleidoscope
tutorials.
As Dave mentioned, I'm also working on some new JIT APIs (Orc) that
2016 Mar 31
1
Kaleidoscope examples on Windows
Are the Kaleidoscope examples supposed to work on Windows? e.g.
C:\llvm\examples\Kaleidoscope\Orc\initial\toy.cpp
when I try to compile this with clang it gives compile time error
messages, and when I try with Microsoft C++ it generates an executable that
runs but crashes when I type in an expression; I get similar results with
a few of the other versions. I can give more detailed feedback if
2011 Apr 17
0
[LLVMdev] Xcode 4 autocomplete of LLVM includes
Jonathan Ragan-Kelley <katokop1 <at> gmail.com> writes:
>
> Slightly off-topic, but I imagine this crowd must have some experience
> using Xcode 4 for projects linking to LLVM. I've actually started
> using Xcode 4 as an IDE for C/C++ development thanks to the vastly
> improved code analysis-based tools it's inherited largely thanks to
> LLVM. But,
2010 Jun 21
1
[LLVMdev] [PATCH] docs/tutorial/ Kaleidoscope typos
On Mon, 21 Jun 2010 15:31:57 -0500, Chris Lattner <clattner at apple.com>
wrote:
> Applied in r106468, thanks!
>
> -Chris
I think there's a few bugs left in the Kaleidoscope tutorial -- I noticed
somebody converted some of the "Builder.CreateAdd" to CreateFAdd, etc., but
there seem to be a few that got missed. Attached diff is what I could
find...
Kevin Kelley
2011 Jan 06
1
[LLVMdev] Build problems and workarounds with CMake and XCode
----- Original Message ----
> From: Óscar Fuentes <ofv at wanadoo.es>
> To: Samuel Crow <samuraileumas at yahoo.com>
> Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
> Sent: Wed, January 5, 2011 5:00:00 PM
> Subject: Re: Build problems and workarounds with CMake and XCode
>
> Samuel Crow <samuraileumas at yahoo.com> writes:
>
>
2015 Jan 16
2
[LLVMdev] Function calls only being JIT'd once by Kaleidoscope with MCJIT?
Oh - I know what this is. You were running this on Linux, right?
On MacOS I think the symbol is getting double mangled while going through
MCJIT::getSymbolAddress, hence the failure: The IR level foo function gets
compiled to "_foo" in the object file, and then "_foo" gets mangled to
"__foo" when we look it up. Linux doesn't do assembly level name-mangling,
so