Displaying 20 results from an estimated 400 matches similar to: "[LLVMdev] Attempt #1: JIT Thread Safety"
2004 Dec 14
0
[LLVMdev] misc. patches
Morten,
The leaks.patch file introduced a static destructor ordering problem
which lead to garbled output. The comment above those lines of code
indicates why it needs to be the way it is. My bad for committing it in
the first place. Please be careful in the future.
Reid.
On Mon, 2004-12-13 at 05:30, Morten Ofstad wrote:
> Hi,
>
> here are some minor patches that for various reasons
2004 Nov 15
0
[LLVMdev] Fixes for windows version
Morten,
I've applied these patches. Thanks for the updates!
Reid.
On Mon, 2004-11-15 at 01:26, Morten Ofstad wrote:
> Hi,
>
> when I updated the sources today there were several small problems that
> stopped the windows version from compiling, here are the patches
>
> m.
>
>
> ______________________________________________________________________
> Index:
2012 Jun 03
0
[LLVMdev] [question] IR<-->native program state mode switch how / where is it done
Hi, all I'm new here so I hope I'm not breaching etiquette or posting in
the wrong list, if so please redirect me.
I'm a student studying the LLVM JIT-Interpreter source and i have a
question:
where and how is the switch/mapping from infinite register IR to native
arch dependent register set managed, to preserve the program state, during
jumps from the Interpreter to the JIT and vice
2005 Mar 16
2
[LLVMdev] Adding system libraries to the LLVM build
I'm back working on my threading patch for the LLVM JIT after being
distracted by a paper deadline. I think I have things working nicely on
Mac OS X (I just did a CVS up and it will take another hour or two to
build), but I'm having an issue with building on Linux. Specifically,
"lli" fails to link because it now needs to link against libpthread,
because it ends up pulling
2005 Mar 16
0
[LLVMdev] Adding system libraries to the LLVM build
On Tue, 15 Mar 2005, Evan Jones wrote:
> I'm back working on my threading patch for the LLVM JIT after being
> distracted by a paper deadline. I think I have things working nicely on Mac
> OS X (I just did a CVS up and it will take another hour or two to build), but
> I'm having an issue with building on Linux. Specifically, "lli" fails to link
> because it now
2008 Feb 28
1
[LLVMdev] Are multiple execution engines allowed?
I'm trying to set up some automated testing, and I'd like to have
multiple instances of ExecutionEngines, so that the state from the
first test doesn't alter the second state.
Right now I'm doing something along the lines of:
Module *emptyModule = new Module("emptyModule");
ExecutionEngine executionEngine = ExecutionEngine::create(emptyModule);
2015 Oct 08
2
llvm:cl::parser subclasses final in 3.7?
All,
I'm upgrading some code that uses LLVM from 3.6 to 3.7. It looks like the
llvm::cl::parser subclasses are now final?
We had been doing:
struct MaxThreadsParser : public llvm::cl::parser<unsigned> {
bool parse(llvm::cl::Option &O, llvm::StringRef ArgName, llvm::StringRef
Arg,
unsigned &Val);
};
But that's now causing:
In file included from
2005 May 26
0
Review about uid and gid mount option
Hi everybody!
I had a problem (now solved) with the UIDs and GIDs assigned to my SMB
filesystem once mounted. I have discovered several things and I wanted
to send my review to the list, maybe you'll find it usefull or maybe you
could add more info.
First of all let's describe the problem: I mount my SMB share (SAMBA
3.0.14a server) on my local filesystem (Linux box), but
2009 Jun 30
2
[LLVMdev] JIT allocates global data in function body memory
> That's me (and I'm not on IRC because I like messages to be
> archived). The reason everything needs to go in the same buffer is
> that we're JITting code on one machine, then sending it to another to
> be executed, and references from one buffer to another won't work in
> that environment. So that model needs to continue to work. If you
> want to generalize
2005 Aug 28
1
[LLVMdev] MutexGuard and MutexLocker
On Sat, 2005-08-27 at 11:47 -0700, Reid Spencer wrote:
> Alkis Evlogimenos wrote:
> > It seems that these two classes are the same... Maybe they should be
> > merged into 1 class?
> >
> I think you're looking at something old. MutexLocker doesn't exist any more.
llvm/Support/ThreadSupport.h is not generated anymore?
--
Alkis
2004 Aug 31
4
[LLVMdev] More configure problems
When I ran configure after updating, I get various errors. First:
% ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i386-unknown-freebsd5.2.1
checking host system type... i386-unknown-freebsd5.2.1
checking target system type... i386-unknown-freebsd5.2.1
test: Unknown: bad
2009 Mar 16
0
[LLVMdev] MachO and ELF Writers/MachineCodeEmittersarehard-codedinto LLVMTargetMachine
Aaron, I mailed in the same mail twice (by mistake), you answered both
copies. Differently!
In any case, I've re-read what exists. I'm dumping what I understand
here, so that we can discuss in detail. I'm using MachO as the example
object format, as the ELF code is totally broken and outdated. Lets
use the following as the basis for our discussion?
There are 3 classes which
2009 Jul 01
0
[LLVMdev] JIT allocates global data in function body memory
On Mon, Jun 29, 2009 at 9:23 PM, Reid Kleckner<rnk at mit.edu> wrote:
>> That's me (and I'm not on IRC because I like messages to be
>> archived). The reason everything needs to go in the same buffer is
>> that we're JITting code on one machine, then sending it to another to
>> be executed, and references from one buffer to another won't work in
2004 Dec 13
6
[LLVMdev] misc. patches
Hi,
here are some minor patches that for various reasons I've not submitted
yet - I'm just trying to clear my list of differences before christmas...
First of all the clear.patch file contains a patch that enables the JIT
to drop all global mappings. I need this because when I have N threads I
compile N different versions of my functions using different memory
areas for global
2004 Aug 31
0
[LLVMdev] More configure problems
On Mon, 30 Aug 2004 20:48:45 -0700
Jeff Cohen <jeffc at jolt-lang.org> wrote:
> When I ran configure after updating, I get various errors. First:
>
> % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc
> checking for a BSD-compatible install... /usr/bin/install -c
> checking build system type... i386-unknown-freebsd5.2.1
> checking host system
2008 Nov 23
1
SendImage()
SendImage() in 1.4:
---cut---
SendImage(filename): Sends an image on a channel.
If the channel supports image transport but the image send
fails, the channel will be hung up. Otherwise, the dialplan
continues execution.
The option string may contain the following character:
'j' -- jump to priority n+101 if the channel doesn't support image transport
This application sets the
2004 Dec 03
0
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
On Fri, 3 Dec 2004, Reid Spencer wrote:
> Could someone please apply this patch to the Win32 support so that
> Morten and Jeff can handle the recent changes? I can't do it because
> I"m on the road with only email access.
I'd be happy to do it. Can someone send me the patch as an attachment
off-list?
-Chris
> > <Tool
> >
2004 Aug 31
2
[LLVMdev] More configure problems
On Mon, 30 Aug 2004 21:27:26 -0700
Jeff Cohen <jeffc at jolt-lang.org> wrote:
> On Mon, 30 Aug 2004 20:48:45 -0700
> Jeff Cohen <jeffc at jolt-lang.org> wrote:
>
> > When I ran configure after updating, I get various errors. First:
> >
> > % ../configure --enable-jit --with-llvmgccdir=/home/llvm/cfrontend/x86/llvm-gcc
> > checking for a
2005 Feb 09
0
[LLVMdev] Interactions with threads and native code
On Tue, 8 Feb 2005, Evan Jones wrote:
> On Feb 8, 2005, at 21:36, Chris Lattner wrote:
>> That is correct. If you try to run threaded programs in the JIT, it might
>> run into problems if multiple functions need to JIT functions at the same
>> time. This should be very simple to deal with, we just haven't had anyone
>> take up the task yet. Only the JIT is
2001 Dec 17
1
CVS update: rsync
On 14 Dec 2001, dwd@samba.org wrote:
> open_socket_in was attempting to try all the protocols returned from
> getaddrinfo(), but only if a corresponding call to socket() returned one of
> three *NOSUPPORT errno codes. A Redhat 6.2 system was observed returning
> EINVAL instead so it never went on to try IPv4. This update adds EINVAL to
> the list. Question: why not always