From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: eggert@cs.ucla.edu, fabrice.popineau@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs-26 threads problem [win64]
Date: Sat, 14 Oct 2017 13:33:07 +0300 [thread overview]
Message-ID: <83mv4uhvdo.fsf@gnu.org> (raw)
In-Reply-To: <m2zi8uvzz4.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 14 Oct 2017 11:30:07 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, fabrice.popineau@gmail.com, emacs-devel@gnu.org
> Date: Sat, 14 Oct 2017 11:30:07 +0200
>
> On Okt 14 2017, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> > Eli Zaretskii wrote:
> >> What is special about this specific struct that it needs such an
> >> alignment?
> >
> > The answer to this question is MS-Windows specific, and I don't know
> > exactly which member of struct thread_state requires 16-byte alignment. I
> > just know it's in there somewhere....
>
> Obvious candidates are sys_thread_t and sys_cond_t, of course.
Can you explain why? E.g., with pthreads, sys_thread_t is pthread_t,
which AFAIU is the same width as 'int', in which case it won't force
any 16-byte alignment anywhere.
Also, all the members which have the sys_thread_t and sys_cond_t types
are after the problematic members in the struct offset order, so how
can they affect the alignment of the problematic members or of the
struct itself?
Thanks.
next prev parent reply other threads:[~2017-10-14 10:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 19:48 Emacs-26 threads problem [win64] Fabrice Popineau
2017-10-10 6:25 ` Eli Zaretskii
2017-10-10 16:13 ` Fabrice Popineau
2017-10-10 16:30 ` Eli Zaretskii
2017-10-10 16:48 ` Eli Zaretskii
2017-10-10 18:57 ` Fabrice Popineau
2017-10-10 19:39 ` Eli Zaretskii
2017-10-10 19:58 ` Fabrice Popineau
2017-10-10 20:09 ` Eli Zaretskii
2017-10-10 20:14 ` Fabrice Popineau
2017-10-11 10:02 ` Eli Zaretskii
2017-10-13 18:52 ` Eli Zaretskii
2017-10-13 22:00 ` Richard Copley
2017-10-14 6:39 ` Eli Zaretskii
2017-10-13 22:28 ` Paul Eggert
2017-10-14 6:47 ` Eli Zaretskii
2017-10-14 8:05 ` Paul Eggert
2017-10-14 8:25 ` Eli Zaretskii
2017-10-14 9:28 ` Paul Eggert
2017-10-14 9:30 ` Andreas Schwab
2017-10-14 10:33 ` Eli Zaretskii [this message]
2017-10-14 11:31 ` Andreas Schwab
2017-10-14 12:18 ` Eli Zaretskii
2017-10-14 12:39 ` Andreas Schwab
2017-10-14 14:00 ` Eli Zaretskii
2017-10-14 22:51 ` Paul Eggert
2017-10-15 15:14 ` Eli Zaretskii
2017-10-15 15:39 ` Andreas Schwab
2017-10-15 16:30 ` Eli Zaretskii
2017-10-15 16:41 ` Stefan Monnier
2017-10-15 17:19 ` Eli Zaretskii
2017-10-15 16:47 ` Andreas Schwab
2017-10-14 9:26 ` Andreas Schwab
2017-10-14 9:31 ` Paul Eggert
2017-10-14 19:06 ` Fabrice Popineau
2017-10-10 18:55 ` Fabrice Popineau
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mv4uhvdo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@gmail.com \
--cc=schwab@linux-m68k.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).