search for: __regparm__

Displaying 12 results from an estimated 12 matches for "__regparm__".

2011 Sep 16
3
[LLVMdev] help with an error message using clang ?
...leanup_fct_attribute; ^~~~~~~~~~~~~~~~~~~~~~~ In file included from TEST.C:46: In file included from /usr/include/stdlib.h:320: In file included from /usr/include/sys/types.h:271: /usr/include/bits/pthreadtypes.h:222:50: note: instantiated from: # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) ^ ~ In file included from TEST.C:65: /usr/include/pthread.h:677:3: error: 'regparm' is not valid on this platform __cleanup_fct_attribute; ^~~~~~~~~~~~~~~~~~~~~~~ In file included from TEST.C:46: In file included from /us...
2011 Sep 16
0
[LLVMdev] help with an error message using clang ?
...  ^~~~~~~~~~~~~~~~~~~~~~~ > In file included from TEST.C:46: > In file included from /usr/include/stdlib.h:320: > In file included from /usr/include/sys/types.h:271: > /usr/include/bits/pthreadtypes.h:222:50: note: instantiated from: > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) >                                                  ^            ~ > In file included from TEST.C:65: > /usr/include/pthread.h:677:3: error: 'regparm' is not valid on this platform >   __cleanup_fct_attribute; >   ^~~~~~~~~~~~~~~~~~~~~~~ > In file included from TEST.C...
2011 Sep 17
1
[LLVMdev] help with an error message using clang ?
...> > In file included from TEST.C:46: > > In file included from /usr/include/stdlib.h:320: > > In file included from /usr/include/sys/types.h:271: > > /usr/include/bits/pthreadtypes.h:222:50: note: instantiated from: > > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > > ^ ~ > > In file included from TEST.C:65: > > /usr/include/pthread.h:677:3: error: 'regparm' is not valid on this > platform > > __cleanup_fct_attribute; > > ^~~~~~~~~~~~~~~~~~~~~~~ &gt...
2020 Jul 28
2
[PATCH] Add syscall wrappers required by libkeyutils
On 2020-07-27 19:20, hpa at zytor.com wrote: > > I'm not so sure they have dealt with it in the sense of having it work on all architectures. *Most* of the problems are related to the shifting the arguments by one, which can cause a bunch of problems, especially if it means the arguments spill to memory. However, I have absolutely no idea how to correctly implement syscall(3) on s390
2018 Dec 10
2
Compiling for baremetal ARMv4 on Ubuntu Linux
...r/include/pthread.h:682:6: error: 'regparm' is not valid on this platform __cleanup_fct_attribute; ^~~~~~~~~~~~~~~~~~~~~~~ /usr/include/bits/pthreadtypes-arch.h:103:50: note: expanded from macro '__cleanup_fct_attribute' # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) ^ ~ In file included from /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/emutls.c:41: /usr/include/pthread.h:694:3: error: 'regparm' is not valid on this platform __cleanup_fct_attribute; ^~~~~~~~~~~~~~~~~~~~~...
2018 Dec 13
2
Compiling for baremetal ARMv4 on Ubuntu Linux
...'regparm' is not valid on this platform >> __cleanup_fct_attribute; >> ^~~~~~~~~~~~~~~~~~~~~~~ >> /usr/include/bits/pthreadtypes-arch.h:103:50: note: expanded from macro '__cleanup_fct_attribute' >> # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) >> ^ ~ >> In file included from /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/emutls.c:41: >> /usr/include/pthread.h:694:3: error: 'regparm' is not valid on this platform >> __cleanup_fct_a...
2018 Dec 14
3
Compiling for baremetal ARMv4 on Ubuntu Linux
...39;regparm' is not valid on this platform > > __cleanup_fct_attribute; > > ^~~~~~~~~~~~~~~~~~~~~~~ > > /usr/include/bits/pthreadtypes-arch.h:103:50: note: expanded from macro '__cleanup_fct_attribute' > > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > > ^ ~ > > In file included from /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/emutls.c:41: > > /usr/include/pthread.h:694:3: error: 'regparm' is not valid on this platform > > __cleanup_fct...
2019 Feb 04
2
Compiling for baremetal ARMv4 on Ubuntu Linux
...is platform > >>> __cleanup_fct_attribute; > >>> ^~~~~~~~~~~~~~~~~~~~~~~ > >>> /usr/include/bits/pthreadtypes-arch.h:103:50: note: expanded from macro '__cleanup_fct_attribute' > >>> # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > >>> ^ ~ > >>> In file included from /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/emutls.c:41: > >>> /usr/include/pthread.h:694:3: error: 'regparm' is not valid on this platform...
2019 Mar 04
2
Compiling for baremetal ARMv4 on Ubuntu Linux
...h:682:6: error: 'regparm' is not valid on this platform > __cleanup_fct_attribute; > ^~~~~~~~~~~~~~~~~~~~~~~ > /usr/include/bits/pthreadtypes-arch.h:103:50: note: expanded from macro '__cleanup_fct_attribute' > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > ^ ~ > In file included from /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/emutls.c:41: > /usr/include/pthread.h:694:3: error: 'regparm' is not valid on this platform > __cleanup_fct_attribute; >...
2019 Mar 11
2
Compiling for baremetal ARMv4 on Ubuntu Linux
...h:682:6: error: 'regparm' is not valid on this platform > __cleanup_fct_attribute; > ^~~~~~~~~~~~~~~~~~~~~~~ > /usr/include/bits/pthreadtypes-arch.h:103:50: note: expanded from macro '__cleanup_fct_attribute' > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > ^ ~ > In file included from /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/emutls.c:41: > /usr/include/pthread.h:694:3: error: 'regparm' is not valid on this platform > __cleanup_fct_attribute; >...
2018 Dec 07
2
Compiling for baremetal ARMv4 on Ubuntu Linux
Hello, on the problems cross-building compiler-rt: Tried to follow https://llvm.org/docs/HowToCrossCompileBuiltinsOnArm.html which lead to this cmake: cmake -G "Ninja" ../llvm/projects/compiler-rt/ -DCOMPILER_RT_BUILD_BUILTINS=ON -DCOMPILER_RT_BUILD_SANITIZERS=OFF -DCOMPILER_RT_BUILD_XRAY=OFF -DCOMPILER_RT_BUILD_LIBFUZZER=OFF -DCOMPILER_RT_BUILD_PROFILE=OFF
2013 Sep 23
57
[PATCH RFC v13 00/20] Introduce PVH domU support
This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.