unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 15 Oct 2017 19:30:16 +0300	[thread overview]
Message-ID: <83h8v0gyqv.fsf@gnu.org> (raw)
In-Reply-To: <874lr0zah1.fsf@linux-m68k.org> (message from Andreas Schwab on Sun, 15 Oct 2017 17:39:38 +0200)

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>,  fabrice.popineau@gmail.com,  emacs-devel@gnu.org
> Date: Sun, 15 Oct 2017 17:39:38 +0200
> 
> > OOC, when a program does
> >
> >   struct foo *ptr = malloc (sizeof struct foo);
> >
> > how is the alignment of the resulting pointer arranged to be "the
> > maximum of the struct members"? 
> 
> RTFM:
> 
>        The malloc() and calloc() functions return a pointer to  the  allocated
>        memory,  which  is  suitably  aligned for any built-in type.

I did, and thus my question: is GCC correct assuming movaps can be
used on a member of an arbitrary struct, if allocating that struct is
not guaranteed to produce the alignment expected by that instruction,
unless the program used aligned_alloc?

Sorry, this sounds like I'm right back to my first question, but
Paul's response seemed to indicate that the required alignment is
guaranteed, and you now seem to say it isn't.  I'm probably missing
something.

Thanks.



  reply	other threads:[~2017-10-15 16:30 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
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 [this message]
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=83h8v0gyqv.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).