From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: rgm@gnu.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: emacs-26 9e59de9: Use GCALIGNED properly for GCC
Date: Fri, 10 Nov 2017 10:06:51 +0200 [thread overview]
Message-ID: <83zi7upnfo.fsf@gnu.org> (raw)
In-Reply-To: <5A0550FE.2030703@gmx.at> (message from martin rudalics on Fri, 10 Nov 2017 08:10:54 +0100)
> Date: Fri, 10 Nov 2017 08:10:54 +0100
> From: martin rudalics <rudalics@gmx.at>
> Cc: Paul Eggert <eggert@cs.ucla.edu>
>
> ... and trying my usual 32-bit build of the release branch on Windows
> currently fails as
Paul, maybe we should simply go back a few notches and not mark
main_thread as GCALIGNED, except on that single platform which needed
it (i.e. via #ifdef)? Then we could return all the other symbols to
their previous syntax.
Or maybe we should move GCALIGNED to yet another position, like at the
beginning or the end of the whole construct. Like this:
GCALIGNED struct foo FOO;
or
struct foo FOO GCALIGNED;
Not sure what else can we do, but this seems to be an exceptionally
fragile feature, at least with GCC 7 that many people are using.
next prev parent reply other threads:[~2017-11-10 8:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171109031206.7056.28312@vcs0.savannah.gnu.org>
[not found] ` <20171109031208.D2CAF2033E@vcs0.savannah.gnu.org>
2017-11-09 23:31 ` emacs-26 9e59de9: Use GCALIGNED properly for GCC Glenn Morris
2017-11-10 7:10 ` martin rudalics
2017-11-10 8:06 ` Eli Zaretskii [this message]
2017-11-10 8:26 ` Paul Eggert
2017-11-10 9:57 ` Eli Zaretskii
2017-11-10 16:23 ` Stefan Monnier
2017-11-10 17:58 ` Paul Eggert
2017-11-10 18:02 ` Stefan Monnier
2017-11-10 18:11 ` Philipp Stephani
2017-11-10 19:19 ` Paul Eggert
2017-11-10 20:31 ` Stefan Monnier
2017-11-10 20:45 ` Paul Eggert
2017-11-11 7:08 ` Paul Eggert
2017-11-11 7:57 ` Paul Eggert
2017-11-11 8:34 ` martin rudalics
2017-11-11 8:50 ` Paul Eggert
2017-11-11 9:46 ` martin rudalics
2017-11-11 8:33 ` martin rudalics
2017-11-13 18:19 ` Paul Eggert
2017-11-13 18:45 ` martin rudalics
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=83zi7upnfo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=rudalics@gmx.at \
/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).