From: John Mastro <john.b.mastro@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: 29183@debbugs.gnu.org
Subject: bug#29183: 27.0.50; SIGSEGV on C-g on Windows
Date: Thu, 9 Nov 2017 09:59:00 -0800 [thread overview]
Message-ID: <CAOj2CQScvxpmg4XN4vrOmLujhgiNGWfeyZPQUwhsck_znnaU1g@mail.gmail.com> (raw)
In-Reply-To: <a0a4ad80-39cb-3543-03af-3b58a547ba8d@cs.ucla.edu>
Paul Eggert <eggert@cs.ucla.edu> wrote:
> John Mastro wrote:
>>
>> the only line in the diff between the two resulting
>> files that mentions main_thread is that the output from the source with
>> GCALIGNED says:
>>
>> .lcomm main_thread,592,8
>>
>> Whereas the assembly output from the source without GCALIGNED says:
>>
>> .lcomm main_thread,592,32
>
>
> Thanks, this helped me see the problem. It turns out that 'struct foo
> __attribute__ ((aligned (8)))' does not work with GCC, and that one must put
> the attribute somewhere else. This appears to be a bug in GCC, and I
> reported the GCC bug here:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82914
>
> The workaround is easy: say 'struct __attribute__ ((aligned (8))) foo'
> instead. I installed the attached patch into the emacs-26 branch and merged
> it into master. Please give it a try.
I can confirm that fixed it. Thank you both!
John
next prev parent reply other threads:[~2017-11-09 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 21:58 bug#29183: 27.0.50; SIGSEGV on C-g on Windows John Mastro
2017-11-07 3:36 ` Eli Zaretskii
2017-11-07 18:14 ` John Mastro
2017-11-07 19:41 ` Eli Zaretskii
2017-11-07 21:24 ` John Mastro
2017-11-08 3:43 ` Eli Zaretskii
2017-11-08 18:35 ` John Mastro
2017-11-08 18:53 ` Eli Zaretskii
2017-11-08 22:46 ` Paul Eggert
2017-11-08 23:41 ` John Mastro
2017-11-09 4:56 ` Paul Eggert
2017-11-09 17:59 ` John Mastro [this message]
2017-11-09 14:59 ` Davor Rotim
2017-11-09 17:04 ` Eli Zaretskii
2017-11-09 18:10 ` Davor Rotim
2017-12-01 10:00 ` Noam Postavsky
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=CAOj2CQScvxpmg4XN4vrOmLujhgiNGWfeyZPQUwhsck_znnaU1g@mail.gmail.com \
--to=john.b.mastro@gmail.com \
--cc=29183@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.