From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rcopley@gmail.com, 29040@debbugs.gnu.org
Subject: bug#29040: Emacs 25 hangs on windows arbitrarily during search of a unicode file
Date: Fri, 03 Nov 2017 10:37:41 +0200 [thread overview]
Message-ID: <83d14zwyei.fsf@gnu.org> (raw)
In-Reply-To: <8d805311-7837-681b-55c0-32e61c8a3b60@cs.ucla.edu> (message from Paul Eggert on Thu, 2 Nov 2017 22:03:17 -0700)
> Cc: rcopley@gmail.com, 29040@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 2 Nov 2017 22:03:17 -0700
>
> > I don't know anything about that code, and I don't think anyone does.
> > Who will tell us that the comment is still accurate?
>
> Since MSVC is no longer relevant, it doesn't matter whether the comment about
> MSVC is accurate, and we can remove it.
Alpha was never relevant for the MS-Windows builds, either, but we
still had this code since about forever.
But my point was that I'm not sure this isn't needed for the GCC build
on Windows. I don't know enough about how GNU ld generates MS-Windows
executables to tell whether this could be so. If you feel strongly
about getting rid of those 2 lines, I guess it's okay to try that on
master.
next prev parent reply other threads:[~2017-11-03 8:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 13:40 bug#29040: emacs-26 crash due to misaligned longjmp buffer in 64-bit MSYS2/MinGW-W64 build Richard Copley
2017-10-28 13:55 ` Eli Zaretskii
2017-10-28 14:10 ` bug#29040: Trouble with misaligned jmp_buf in 64-bit MinGW-64 runtime, in Emacs 26 Richard Copley
2017-11-02 6:02 ` bug#29040: Emacs 25 hangs on windows arbitrarily during search of a unicode file Paul Eggert
2017-11-02 7:43 ` Richard Copley
2017-11-02 11:10 ` Noam Postavsky
2017-11-02 15:50 ` Eli Zaretskii
2017-11-02 20:35 ` Paul Eggert
2017-11-02 20:46 ` Eli Zaretskii
2017-11-03 5:03 ` Paul Eggert
2017-11-03 8:37 ` Eli Zaretskii [this message]
2017-11-03 8:48 ` Paul Eggert
2017-11-03 8:50 ` Eli Zaretskii
2017-11-03 9:25 ` Paul Eggert
2017-11-03 10:02 ` Eli Zaretskii
[not found] <CAGdT1gr9mOiB7Vcx+adyknAfpvTiUSZuxZzAXJo7ivh91HMgww@mail.gmail.com>
[not found] ` <837evrerok.fsf@gnu.org>
[not found] ` <CAPM58ojq+XSimHbAF8kt=0GBPTfX+9XkWdkfj0cJ_EPz-=Y_-A@mail.gmail.com>
[not found] ` <83mv4b5x0y.fsf@gnu.org>
[not found] ` <CAPM58oj0xajqLUowznia7z=d6yL7Qk4AqbaL9KzKnJw7EXPY=w@mail.gmail.com>
[not found] ` <83inez5uta.fsf@gnu.org>
[not found] ` <CAPM58oj9AnC90N+NiS4z_wP3EO5Xz3QtgdZUONqXLyhYR94NPA@mail.gmail.com>
[not found] ` <CAPM58oj6HBWkv0K=M0iy1xVPqQ0JTtFCEAZG8oW2SMrO8-XkcA@mail.gmail.com>
[not found] ` <83fua35tem.fsf@gnu.org>
2017-10-28 13:56 ` Richard Copley
2017-10-28 14:14 ` Eli Zaretskii
2017-10-28 15:58 ` Eli Zaretskii
2017-10-28 16:16 ` Richard Copley
2017-10-28 16:41 ` Eli Zaretskii
2017-10-29 18:10 ` Richard Copley
2017-11-01 19:16 ` Richard Copley
2017-11-02 7:39 ` Richard Copley
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=83d14zwyei.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29040@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=rcopley@gmail.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.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).