From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Copley Newsgroups: gmane.emacs.bugs Subject: bug#29040: Emacs 25 hangs on windows arbitrarily during search of a unicode file Date: Thu, 2 Nov 2017 07:43:34 +0000 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1509608719 14318 195.159.176.226 (2 Nov 2017 07:45:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 2 Nov 2017 07:45:19 +0000 (UTC) Cc: 29040@debbugs.gnu.org To: Paul Eggert Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Nov 02 08:45:14 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAABZ-0002m8-54 for geb-bug-gnu-emacs@m.gmane.org; Thu, 02 Nov 2017 08:45:09 +0100 Original-Received: from localhost ([::1]:59050 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eAABg-00021M-2D for geb-bug-gnu-emacs@m.gmane.org; Thu, 02 Nov 2017 03:45:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39338) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eAABV-00020w-Lc for bug-gnu-emacs@gnu.org; Thu, 02 Nov 2017 03:45:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eAABS-0008Nr-IS for bug-gnu-emacs@gnu.org; Thu, 02 Nov 2017 03:45:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:38124) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eAABS-0008Nn-EX for bug-gnu-emacs@gnu.org; Thu, 02 Nov 2017 03:45:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eAABS-0008Cu-7A for bug-gnu-emacs@gnu.org; Thu, 02 Nov 2017 03:45:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Richard Copley Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 02 Nov 2017 07:45:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 29040 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 29040-submit@debbugs.gnu.org id=B29040.150960865231469 (code B ref 29040); Thu, 02 Nov 2017 07:45:02 +0000 Original-Received: (at 29040) by debbugs.gnu.org; 2 Nov 2017 07:44:12 +0000 Original-Received: from localhost ([127.0.0.1]:46804 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAAAd-0008BV-OW for submit@debbugs.gnu.org; Thu, 02 Nov 2017 03:44:12 -0400 Original-Received: from mail-oi0-f52.google.com ([209.85.218.52]:45793) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAAAc-0008BI-5P for 29040@debbugs.gnu.org; Thu, 02 Nov 2017 03:44:10 -0400 Original-Received: by mail-oi0-f52.google.com with SMTP id f66so7691791oib.2 for <29040@debbugs.gnu.org>; Thu, 02 Nov 2017 00:44:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sdSJf2o10zFx1geOOrsIA95zHB5WGJjY8FYQv9raSnw=; b=bqCCaZdf6LqitwWMS8MORTuVMKiNpRJ3UzBzY2n8WABEHrmAS4wWrT0RcmeGoeMYSR uQtMW53Zsj/vkA6TnkBrb3qPuot/N31r4nnlzj2cNMLKQu3Rvtf6z6h4tGs9+kNh/wTp vLXTUOVuWYrhJcJHJnToP4morUFh+bnXnGep4Snhy84CB1P4LMbMSoXFHFE23Qsi23N0 rWfRrxGWWrnKvjyqBkCwujIpziakBu3Ibi9Dba/xQf+Nalakc85Tp1Al8iJ+2KPC/79h YG5houZW6P2DbHaCIkEg/ogdO3bPRT1I5FtZHLYzloRe4cKXrfaC51dJ7kFCOXW1PQK7 At1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sdSJf2o10zFx1geOOrsIA95zHB5WGJjY8FYQv9raSnw=; b=E3JBB1KrLGDKhPtkt4Zq5WpfUO55fyy3HIkp4JA1te3hvxjvpVxSAJaBfRatlutTgB VPZ01ulHvfEzQx5L1J/DMeDI2oiMqT9MTAelavXRsIGgQJ724vKjvrSAZ4oz0NxYnz8P u0kbDnSW4WBCjPzYYGEFfuWS3yQ8OsQdenPrhuT91l7mBqQbylil3VBEx3pdHwPBiEzN EFSejkDBsV/YeZUktU0SRzcI5Ds3nc+IixO0z1ojeaYvtUrrggVpk2jLmCrRsNGeJ8D9 QF/VSrsAn/RTfjCsnQLUXmcoG30zTMHEv0yg4XbRDNkl5uQtk62VSdRrIabeoRlax86l jIKg== X-Gm-Message-State: AMCzsaUP7UNZYpjzTvfx6mjKKbf6Lp/BCwmdBjrRWM7RwPpI84d4C8/F nQ5SNM2kFYKnbXvg6sQXx2m/MGBPR07TQQw3TbyvnJMW X-Google-Smtp-Source: ABhQp+QinISfd3YWurNGSj6Y9/37wbzS+wK19u6frYZ89aFmxcRsPR9clxb2fiji0Y772wBODJu0JuxhkJPnAdhmweg= X-Received: by 10.202.11.3 with SMTP id 3mr1474685oil.71.1509608644619; Thu, 02 Nov 2017 00:44:04 -0700 (PDT) Original-Received: by 10.157.64.8 with HTTP; Thu, 2 Nov 2017 00:43:34 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:139354 Archived-At: On 2 November 2017 at 06:02, Paul Eggert wrote: >> +#define THREAD_ALIGNMENT COMMON_MULTIPLE (alignof (max_align_t), >> GCALIGNMENT) >> + >> +static struct thread_state alignas (THREAD_ALIGNMENT) main_thread; > > Three questions: > > The Gnulib manual > > says, "Some compilers require the operand of _Alignas/alignas to be a single > integer constant, not an expression: MSVC 7.0 through at least 10.0." (Also, > > suggests that this issue may also occur with VS2013, though VS2015 should be > OK since it supports alignas.) Are any of these older compilers of concern > when building Emacs? I don't think so. How would one go about building Emacs with MSVC anyway? >If so, the above change won't work for them. > Why does the above code use 'alignof (max_align_t)' rather than 'alignof > (struct thread_state)'? Doesn't the latter suffice? For information, in the 64-bit GCC 7.2 toolchain from MinGW-W64, the two are equal in value. > C11 requires that a compiler must issue a diagnostic for a declaration like > 'struct thread_state alignas (8) foo;' if the alignment of plain 'struct > state' is greater than 8. Can I take it from this bug report that the > Microsoft compilers do not conform to that part of the standard? Microsoft compilers weren't mentioned at all. GCC didn't issue a diagnostic. > If so, we should add checks to verify this requirement where it is assumed elsewhere. I think that is a good idea. Thanks.