similar to: RFT: klibc 2.0.5

I've now been able to test shared-library builds: 2.0.4 2.0.5 -------------------------------------------------------------------- alpha/alpha-linux-gnu: fail: fcntl, sigint, 2c fail: sigint, 2c arm/arm-linux-gnueabi: pass pass arm/arm-linux-gnueabihf: pass pass

On Sun, 2019-01-20 at 04:37 +0000, Ben Hutchings wrote: [...] > ppc/powerpc-linux-gnu: pass fail: malloctest2*, > setjmptest*, sigint* [...] > s390x/s390x-linux-gnu: fail: fcntl fail: malloctest2*, setjmptest* setjmptest*, >

My test script is now published at https://git.kernel.org/pub/scm/linux/kernel/git/bwh/klibc-maint.git/ I found and fixed another bug in QEMU's userland emulation, specific to sparc. I fixed three bugs in klibc. With those changes, the test results are: 2.0.4 2.0.5 master

hello vorlon, got notified of your patch, will apply next days upstream unless some critiques are voiced on ml. thanks. -- maks ----- Forwarded message from Steve Langasek <steve.langasek at canonical.com> ----- Date: Wed, 16 Feb 2011 22:05:42 -0000 From: Steve Langasek <steve.langasek at canonical.com> Subject: [Bug 527720] Re: thumb2 porting issues identified: klibc uses

It seems checkpatch errors krept in, this is a first go. Next run will go into usr/kinit directory. No code changes, just codingstyle fixes (verified with size(3)). maximilian attems (5): [klibc] sleep: have argument on next line [klibc] readklink: remove unneeded braces [klibc] mount: whitespace policy [klibc] ls: fix various checkpatch complaints [klibc] tests: checkpatch fixlets

Hi Ben, *massive* thanks for picking up klibc work. This might motivate me to pick up some of the TODOs for it that have piled on in my TODO (but only after the freeze, I?m sorry to say, I have more to do for other packages). >And I spotted another test program that has this property (setjmptest setjmp is a good topic? I found that building mksh and running its testsuite is a good test to

On Sun, 2019-01-20 at 14:18 +0000, Thorsten Glaser wrote: > Hi Ben, > > *massive* thanks for picking up klibc work. This might motivate > me to pick up some of the TODOs for it that have piled on in my > TODO (but only after the freeze, I?m sorry to say, I have more > to do for other packages). > > >And I spotted another test program that has this property >

Hello, I'm trying to create a pure LLVM toolchain (that will not depend on GNU and produce GNU-free code too) on a musl based distribution. For now, I use gcc to bootstrap and build all LLVM components. I do it individually because I was running out of space and memory trying to build all using LLVM_ENABLE_PROJECTS. Also, I don't want to create a all-in-one package. Then, once

From: Heiko Carstens <heiko.carstens@de.ibm.com> vfork support for s390/s390x. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- diff -purN a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def --- a/usr/klibc/SYSCALLS.def 2006-06-07 09:44:33.000000000 +0200 +++ b/usr/klibc/SYSCALLS.def 2006-06-07 13:01:54.000000000 +0200 @@ -28,7 +28,7 @@ void _exit,exit::_exit(int) ; A

Hello all, I really want to support vfork() in klibc, mostly because uClinux *has* to use it. Unfortunately vfork() isn't allowed to use the stack *at all* across the system call -- including return address -- which means it needs an assembly wrapper on most architectures. I have tried implementing wrappers for most architectures, but I don't know parisc or s390/s390x well enough,

[klibc] Simple test suite for klibc A very simple handful of tests for klibc. This is not by any means an exhaustive test suite, nor are most of the tests auto-verifying, but they are very useful to spot common porting problems. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit b64a5142ab2aa6c030b2a254eb94384161f93f0c tree 84a5bea0d108e9365018d4698548764be7dc68ea parent

kbuild: add klibc/tests to kbuild Add a kbuild file so we now can build the test programs. A new dedicated target is used: make test Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- commit 5492ae07007399d8838dea5f44b3d9cf3603abc3 tree 4339d2d3aa0e80bc81ac0cd8ca3b7c89486b2150 parent 64dda666c087b6e537892ac9984aff57d2b32c47 author Sam Ravnborg <sam@mars.(none)> Sun, 07 Aug 2005

Hi, Having recently enabled IAS by default for the MIPS O32 ABI, I'm now trying to do the same thing for the MIPS N64 ABI. Unfortunately, it is not currently possible to enable IAS by default for the N64 ABI without also enabling it for the N32 ABI because this information is not reflected in the triple and that's the only information MipsMCAsmInfo has. This would be fine if it N32 was

New architectures only define the renameat2() system call, which was added in Linux 3.15. Define rename() and renameat() as wrappers for it if necessary. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- --- a/usr/klibc/Kbuild +++ b/usr/klibc/Kbuild @@ -59,7 +59,8 @@ klib-y += vsnprintf.o snprintf.o vsprint inet/inet_ntoa.o inet/inet_aton.o inet/inet_addr.o \

On 24 June 2016 at 06:02, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > Having recently enabled IAS by default for the MIPS O32 ABI, I'm now trying to do the same thing for the MIPS N64 ABI. Unfortunately, it is not currently possible to enable IAS by default for the N64 ABI without also enabling it for the N32 ABI because this information is not reflected in

Hi Eric, It's the unsolved problems on the pass-MCTargetOptions-everywhere path that are my main concern with that approach rather than the amount of work. The first problem is that the result of IRObjectFile::CollectAsmUndefinedRefs() depends on the ABI but IRObjectFile doesn't know it. How would you deliver the ABI to IRObjectFile? The second problem is that IRLinker will link

On 11 May 2017 at 18:30, Michael Clark via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I note that on your bug that you have stated that the branch is faster than > the conditional move. Faster code is a side effect of the fix in this > particular case. On the contrary: the faster code is pretty much the only reason this can happen before the rest of the FENV support lands.

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---