similar to: [LLVMdev] lib/System Changes

Displaying 20 results from an estimated 300 matches similar to: "[LLVMdev] lib/System Changes"

2004 Sep 11
0
[LLVMdev] lib/System Changes
There is a typo that breaks FreeBSD: Compiling Memory.cpp In file included from /usr/home/llvm/lib/System/Memory.cpp:28: /usr/home/llvm/obj/lib/System/platform/Memory.cpp: In static member function `static void llvm::sys::Memory::ReleaseRWX(llvm::sys::Memory&)': /usr/home/llvm/obj/lib/System/platform/Memory.cpp:47: error: `sterror' undeclared (first use this function)
2004 Sep 15
1
[LLVMdev] Cygwin and FreeBSD broken
The new method Memory::ReleaseRWX has the wrong signature on these two platforms. The argument type is Memory& when it should be MemoryBlock&.
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 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
2020 Aug 22
0
[ANNOUNCE] klibc 2.0.8
I have released version 2.0.8. This is available in the git repository at: https://git.kernel.org/pub/scm/libs/klibc/klibc.git and as a tarball at: https://mirrors.kernel.org/pub/linux/libs/klibc/2.0/ New features: - Support for building with clang and lld, at least on x86 - Defined sysconf(), initially supporting only _SC_PAGE_SIZE - Defined clearerr() as extern - Defined stdio
2001 Jul 23
1
forwarded message from mouring@etoh.eviladmin.org
On Mon, Jul 23, 2001 at 12:49:14AM +0100, Matthew Vernon wrote: > ------- start of forwarded message ------- > From: <mouring at etoh.eviladmin.org> > To: Matthew Vernon <matthew at empire.ucam.org> > cc: <openssh-unix-dev at mindrot.org> > Subject: Re: [patch] GNU/Hurd compatibility patches > Date: Sun, 22 Jul 2001 12:39:32 -0500 (CDT) > > > We
2012 Nov 27
0
[LLVMdev] mmap and vm_protect on ARM+Apple systems
On Nov 16, 2012, at 4:12 PM, "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote: > “ARM Darwin can't do this. Memory is never allowed to be both writable and executable at the same time.” > > That seems very sensible. So do the JIT engines just not work there now? They work by allocating RW memory, then switching the permissions to RX before running any code
2012 Nov 16
0
[LLVMdev] mmap and vm_protect on ARM+Apple systems
Hi Andy, On Nov 16, 2012, at 1:56 PM, "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote: > Hi, > > Can anyone tell me something about mmap and vm_protect on ARM+Apple systems? Some. :) > > I’m working on a new memory manager implementation for MCJIT and I want to replace calls to Memory::AllocateRWX with calls to Memory::allocateMappedMemory, possibly still
2012 Nov 16
2
[LLVMdev] mmap and vm_protect on ARM+Apple systems
Hi, Can anyone tell me something about mmap and vm_protect on ARM+Apple systems? I'm working on a new memory manager implementation for MCJIT and I want to replace calls to Memory::AllocateRWX with calls to Memory::allocateMappedMemory, possibly still with the RWX flags. However, looking at the Memory::AllocateRWX implementation I see that it's jumping through some hoops in the case
2012 Nov 17
4
[LLVMdev] mmap and vm_protect on ARM+Apple systems
"ARM Darwin can't do this. Memory is never allowed to be both writable and executable at the same time." That seems very sensible. So do the JIT engines just not work there now? Currently both MCJIT and JIT are using AllocateRWX which on that platform mmap's the memory as RX, then vm_protect's it as RX+VM_PROT_COPY, then vm_protect's it as RW. My best guess is that
2018 Nov 29
6
[nbdkit PATCH 0/3] Fix %m usage on BSD
Our use of "%m" in various error messages is testament to the project's initial life on Linux - but other than Cygwin, I know of no other platforms supporting that glibc extension. We COULD audit the code and manually turn "%m" into "%s"/strerror(errno), but that's a lot of churn. Instead, let's fix the few outliers that can't be easily wrapped, then
2013 May 13
0
[klibc:sysconf] Framework and trivial implementation of sysconf(3)
Commit-ID: 0e725b1ec953aafa7cec75a22436319e945f93e1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0e725b1ec953aafa7cec75a22436319e945f93e1 Author: H. Peter Anvin <hpa at linux.intel.com> AuthorDate: Mon, 13 May 2013 11:36:38 -0700 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Mon, 13 May 2013 11:36:38 -0700 [klibc] Framework and trivial
2020 Jul 25
0
[klibc:master] tests: Add a trivial test for sysconf()
Commit-ID: 3df6e74ab78fc63aa025d07fb849ec9508cbf1c2 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3df6e74ab78fc63aa025d07fb849ec9508cbf1c2 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 25 Jul 2020 22:46:16 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 22:51:45 +0100 [klibc] tests: Add a trivial test
2020 Jul 25
0
[klibc:master] tests: Add a trivial test for sysconf()
Commit-ID: eae5223098f32ba5cbb83631cec2579f764ee6ff Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=eae5223098f32ba5cbb83631cec2579f764ee6ff Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 25 Jul 2020 22:48:23 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 22:48:23 +0100 [klibc] tests: Add a trivial test
2003 May 10
0
Small Makefile.in Patch
This is a fairly inconsequential patch, but it comes in handy in a few instances. The patch simply splits install-files into "install-files" and "install-sysconf" - taking all of the sysconfdir stuff and putting in its own target which I then added to 'install' and 'install-nokeys'. I then added an install-nosysconf to NOT do that stuff. This helped us
2020 Sep 18
0
[PATCH common] mlutils: Simple wrapper around sysconf (_SC_NPROCESSORS_ONLN).
--- mlutils/unix_utils-c.c | 15 +++++++++++++++ mlutils/unix_utils.ml | 5 +++++ mlutils/unix_utils.mli | 9 +++++++++ 3 files changed, 29 insertions(+) diff --git a/mlutils/unix_utils-c.c b/mlutils/unix_utils-c.c index 3309961..8acf039 100644 --- a/mlutils/unix_utils-c.c +++ b/mlutils/unix_utils-c.c @@ -77,6 +77,7 @@ extern value guestfs_int_mllib_mkdtemp (value val_pattern); extern value
2001 Jun 07
0
Patch for systems with no setreuid()
Sorry if I'm duplicating an existing patch, but... On systems with no seteuid() that have setreuid() there is an emulation, but if both are lacking (but we do have setresuid()), nothing is done. The following seems to be right, but I've only got one machine (running an ancient version of HP-UX) which needs this so it may not be general: --cut-here-- --- config.h.in.orig Thu Jun 7
2013 Jan 18
0
Wine release 1.5.22
The Wine development release 1.5.22 is now available. What's new in this release (see below for details): - New version of the Gecko engine. - Beginnings of the Mac graphics driver. - Support for ARM64 platforms. - Fixes for RTL text in Uniscribe. - Various bug fixes. The source is available from the following locations:
2008 Feb 10
0
Possible VCPU hotplug bug
I am working on a project that uses OpenMP along with Xen''s VCPU hotplug feature. The OpenMP libraries are used for writing multi-threaded applications, and they have a function named omp_get_num_procs() that is used to determine the number of processors available on the system. I noticed that when using the xm vcpu-set command in Xen to change the number of vcpus assigned to a domU
2004 Dec 06
1
[Patch] Makefile.in, new install-nosysconf target
For various reasons, it makes our life easier at USC to have a 'install-nosysconf' target much like the install-nokeys target that was added a while back. I mentioned this a few months back on this list and people seemed to think it wouldn't be a problem to get it into the mainline tree. I've attached the patch -- it should keep 100% backwards compatibility. Thanks. -- Phil