syscfg: Add ARC architecture
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): C2D7FE5348E1B147BCA15975FBA23075012B095AC0@us01wembx1.internal.synopsys.com
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH 1/1 syscfg: Add ARC architecture
Quoted 19 lines · Werner Koch
Quoted 2 lines · On Tue, 18 Sep 2018 21:34, Vineet.Gupta1 at synopsys.com said:
I'm not exactly clear what the question is ? What is specific in ABI related to locks ?
Libgpg-error abstracts the native lock interface and thus needs to get some information on the actual implementation. It can very well be the case that the big-endian ABI is different from the little endian ABI. In particular the static initialization may be different; this is implemented in libgpg-error using a macro which may look like this
#define GPGRT_LOCK_INITIALIZER {1,{{167,171,170,50,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0}}}
Quoted 2 lines
This is an memory image and we can't make use of C data types because we don't know them.
Well BE will certainly be different than LE.
Back to the original discussion, was the question about glibc vs. uClibc pthread ABI ? Since they are different / independent implementations (even if uClibc is sort of copy over from glibc) we can't guarantee that these would the same so each would need a specific initializer I guess.
-Vineet
PATCH 1/1 syscfg: Add ARC architecture
Hi Vineet, Werner,
Quoted 21 lines · Vineet Gupta
Quoted 20 lines · Werner Koch
Quoted 2 lines · On Tue, 18 Sep 2018 21:34, Vineet.Gupta1 at synopsys.com said:
I'm not exactly clear what the question is ? What is specific in ABI related to locks ?
Libgpg-error abstracts the native lock interface and thus needs to get some information on the actual implementation. It can very well be the case that the big-endian ABI is different from the little endian ABI. In particular the static initialization may be different; this is implemented in libgpg-error using a macro which may look like this
#define GPGRT_LOCK_INITIALIZER {1,{{167,171,170,50,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0, \ 0,0,0,0,0,0,0,0}}}
Quoted 8 lines
Quoted 2 lines
This is an memory image and we can't make use of C data types because we don't know them.
Well BE will certainly be different than LE.
Back to the original discussion, was the question about glibc vs. uClibc pthread ABI ? Since they are different / independent implementations (even if uClibc is sort of copy over from glibc) we can't guarantee that these would the same so each would need a specific initializer I guess.
That's what I've got for glibc case:
-------------------------->8------------------------- ## lock-obj-pub.arc-buildroot-linux-gnu.h
## File created by gen-posix-lock-obj - DO NOT EDIT ## To be included by mkheader into gpg-error.h
typedef struct
{
long _vers;
union {
volatile char _priv[24];
long _x_align;
long *_xp_align; } u;
} gpgrt_lock_t;
#define GPGRT_LOCK_INITIALIZER {1,{{0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0}}}##
## Local Variables:
## mode: c
## buffer-read-only: t
## End:
## -------------------------->8-------------------------
I'd say it looks similar to uClibc version which is below as a reference:
-------------------------->8------------------------- ## lock-obj-pub.arc-buildroot-linux-uclibc.h
## File created by gen-posix-lock-obj - DO NOT EDIT ## To be included by mkheader into gpg-error.h
typedef struct
{
long _vers;
union {
volatile char _priv[24];
long _x_align;
long *_xp_align; } u;
} gpgrt_lock_t;
#define GPGRT_LOCK_INITIALIZER {1,{{0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0}}}##
## Local Variables:
## mode: c
## buffer-read-only: t
## End:
## -------------------------->8-------------------------
-Alexey
PATCH 1/1 syscfg: Add ARC architecture
Quoted 2 lines · Alexey.Brodkin at synopsys.com
I'd say it looks similar to uClibc version which is below as a reference:
Ack. I added it to the list.
Shalom-Salam,
Werner
Signature · 8 lines
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-snps-arc/attachments/20180921/dac2f7d0/attachment.sig>