search for: __write

...ive function with the same name for all archs (e.g. __alloc() ) and then people can include this function __alloc() in their libraries, inlining it or even renaming it just to fit the frontend needs. And this can be useful: every backend should implement this set of functions ( __alloc(), __free(), __write()… just for example) so the frontends can build a library with these functions as they want. I don't know if you get me. > On May 22, 2016, at 9:06 PM, Matthias Braun <matze at braunis.de> wrote: > > >> On May 22, 2016, at 10:31 AM, Lorenzo Laneve via llvm-dev <llvm-d...

...ive function with the same name for all archs (e.g. __alloc() ) and then people can include this function __alloc() in their libraries, inlining it or even renaming it just to fit the frontend needs. And this can be useful: every backend should implement this set of functions ( __alloc(), __free(), __write()… just for example) so the frontends can build a library with these functions as they want. > I don't know if you get me. I think you will need to explain a bit more. We already have such a function, it’s called malloc() and a few LLVM passes assume specific behaviour about it. What prob...

So, the backend should implement "__alloc" that does the same as "malloc" - or something subtly different from "malloc" - and on a Windows machine, how is it different from "HeapAlloc"? And "__write" that is same as UNIX "write", but different from "WriteFile" in Windows? And HOW do you expect the backend to implement these? By calling "malloc"/"HeapAlloc", "write"/"WriteFile"? This is what the C library is for, it provides a se...

...main main() File "/usr/local/mailman/Mailman/Cgi/subscribe.py", line 91, in main mlist.Lock() File "/usr/local/mailman/Mailman/MailList.py", line 159, in Lock self.__lock.lock(timeout) File "/usr/local/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/usr/local/mailman/Mailman/LockFile.py", line 424, in __write fp.close() IOError: [Errno 28] No space left on device I realize that this message probably won''t make it to the list, given the above problems, but I figured I''d try just for the hell of it.. M...

Rails People, I like the Rails mail-list. I find a lot of good info here. Can anyone recommend a good mail-list which discusses the usage of HTML, CSS, JavaScript and Ajax? -Peter -- Peter Smith GoodJobFastCar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org http://GoodJobFastCar.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the

...s petersson <mats at planetcatfish.com> wrote: > > So, the backend should implement "__alloc" that does the same as "malloc" - or something subtly different from "malloc" - and on a Windows machine, how is it different from "HeapAlloc"? And "__write" that is same as UNIX "write", but different from "WriteFile" in Windows? And HOW do you expect the backend to implement these? By calling "malloc"/"HeapAlloc", "write"/"WriteFile"? > > This is what the C library is for, it pro...

> On May 22, 2016, at 10:31 AM, Lorenzo Laneve via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > My idea is an API where anyone can build a Runtime Library for any backend, including a set of functions people can inline/rename creating functions the frontend can include in the IR. > > For example implementing a cross-platform runtime function that allocates memory

....h> int *__errno_location(void) { return __error (); } unsigned long int __strtoul_internal(const char *__nptr, char **__endptr, int __base, int __group) { return strtoul (__nptr, __endptr, __base); } void __terminate() { fprintf (stderr, "terminate!\n"); } ssize_t __write (int __fd, const void *__buf, size_t __size) { return write (__fd, __buf, __size); } int __fxstat(int __ver, int __filedesc, struct stat *__stat_buf) { return fstat (__filedesc, __stat_buf); } int __xstat(int __ver, const char *__filename, struct stat *__stat_buf) { return stat (__filena...

My idea is an API where anyone can build a Runtime Library for any backend, including a set of functions people can inline/rename creating functions the frontend can include in the IR. For example implementing a cross-platform runtime function that allocates memory for a new object. (Obviously the library will have to be compiled for each target). I read about compiler-rt but I think it has

I am running Fedora 8 uname -r = 2.6.24.4-64.fc8 on my box with Wine 0.9.58. When I first installed it I noticed that my CPU usage jumped and stayed at 100% with wineserver taking > 85%. I killed the wineserver process and it dropped down, however it soon jumped back up when wineserver restarted itself. I then killed it again and all related processes and disabled it from starting as a damen

...ecking for __fcntl... no > checking for getdents... no > checking for _getdents... no > checking for __getdents... no > checking for _lseek... no > checking for __lseek... no > checking for _read... no > checking for __read... no > checking for _write... no > checking for __write... no > checking for _fork... no > checking for __fork... no > checking for _stat64... no > checking for __stat64... no > checking for _fstat64... no > checking for __fstat64... no > checking for _lstat64... no > checking for __lstat64... no > checking for __sys_llseek......

...hdir... no checking for _fcntl... yes checking for __fcntl... no checking for getdents... yes checking for _getdents... yes checking for __getdents... no checking for _lseek... yes checking for __lseek... no checking for _read... yes checking for __read... no checking for _write... yes checking for __write... no checking for _fork... yes checking for __fork... no checking for _stat64... yes checking for __stat64... no checking for _fstat64... yes checking for __fstat64... no checking for _lstat64... yes checking for __lstat64... no checking for __sys_llseek... no checking for llseek... yes checking f...

...fchdir... yes checking for _fcntl... no checking for __fcntl... yes checking for getdents... no checking for _getdents... no checking for __getdents... no checking for _lseek... no checking for __lseek... yes checking for _read... no checking for __read... yes checking for _write... no checking for __write... yes checking for _fork... yes checking for __fork... yes checking for _stat64... no checking for __stat64... no checking for _fstat64... no checking for __fstat64... no checking for _lstat64... no checking for __lstat64... no checking for __sys_llseek... no checking for llseek... no checking for...

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Now all the comments so far have been addressed, but only a few exceptions. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops.

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Now all the comments so far have been addressed, but only a few exceptions. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops.

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Please review and comments. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops. Currently only ia64/xen pv_ops implementation

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Please review and comments. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops strategy is appropriate too. Later I'll post the patchset which implements xen domU based on ia64/pv_ops. Currently only ia64/xen pv_ops implementation

...r __fchdir... no checking for _fcntl... no checking for __fcntl... no checking for getdents... no checking for _getdents... no checking for __getdents... no checking for _lseek... no checking for __lseek... no checking for _read... no checking for __read... no checking for _write... no checking for __write... no checking for _fork... no checking for __fork... no checking for _stat64... no checking for __stat64... no checking for _fstat64... no checking for __fstat64... no checking for _lstat64... no checking for __lstat64... no checking for __sys_llseek... no checking for llseek... no checking for _l...

...r __fchdir... no checking for _fcntl... no checking for __fcntl... no checking for getdents... no checking for _getdents... no checking for __getdents... no checking for _lseek... no checking for __lseek... no checking for _read... no checking for __read... no checking for _write... no checking for __write... no checking for _fork... no checking for __fork... no checking for _stat64... no checking for __stat64... no checking for _fstat64... no checking for __fstat64... no checking for _lstat64... no checking for __lstat64... no checking for __sys_llseek... no checking for llseek... no checking for _l...

Hi. This patchset implements ia64/pv_ops support which is the framework for virtualization support. Changes from take 5 are rebased to Linux 2.6.26-rc3, bug fix ivt.S paravirtualization and multi entry point support. I believe these patches can be applied to the linux ia64 repository. On x86 various ways to support virtualization were proposed, and eventually pv_ops won. So on ia64 the pv_ops