From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: c++ abi
Date: Tue, 9 Sep 2014 13:43:52 +0200 [thread overview]
Message-ID: <20140909114352.GK10361@port70.net> (raw)
In-Reply-To: <20140909010406.GJ10361@port70.net>
* Szabolcs Nagy <nsz@port70.net> [2014-09-09 03:04:06 +0200]:
> --- x86_64.glibc.abi 2014-09-09 01:40:22.210277471 +0200
> +++ x86_64.musl.abi 2014-09-09 01:41:04.618487657 +0200
...
> @@ -162 +162 @@
> -x_sched_param(sched_param, size (*) [4], align (*) [4])
> +x_sched_param(sched_param, size (*) [48], align (*) [8])
...
> @@ -267 +267 @@
> -x_pthread_rwlockattr_t(pthread_rwlockattr_t, size (*) [8], align (*) [8])
> +x_pthread_rwlockattr_t(pthread_rwlockattr_t, size (*) [8], align (*) [4])
...
> @@ -317 +317 @@
> -x_sem_t(sem_t, size (*) [32], align (*) [8])
> +x_sem_t(sem_t, size (*) [32], align (*) [4])
...
> @@ -360,2 +360,2 @@
> -x_quad_t(long, size (*) [8], align (*) [8])
> -x_rlim_t(unsigned long, size (*) [8], align (*) [8])
> +x_quad_t(long long, size (*) [8], align (*) [8])
> +x_rlim_t(unsigned long long, size (*) [8], align (*) [8])
> @@ -363 +363 @@
> -x_rusage(rusage, size (*) [144], align (*) [8])
> +x_rusage(rusage, size (*) [272], align (*) [8])
> @@ -381,2 +381,2 @@
> -x_cmsghdr(cmsghdr, size (*) [16], align (*) [8])
> -x_fd_mask(long, size (*) [8], align (*) [8])
> +x_cmsghdr(cmsghdr, size (*) [16], align (*) [4])
> +x_fd_mask(unsigned long, size (*) [8], align (*) [8])
cant the different size/alignment cause abi issues
when these types are used embedded into a struct?
and in case of rlim_t if it is used as an argument
to a c++ function
(the omitted diffs are known issues or not relavant to abi compat
i think)
next prev parent reply other threads:[~2014-09-09 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 1:04 Szabolcs Nagy
2014-09-09 11:43 ` Szabolcs Nagy [this message]
2014-09-09 15:00 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140909114352.GK10361@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).