From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16615@debbugs.gnu.org
Subject: bug#16615: 24.3.50; Fatal error visiting a directory (same as #16132?)
Date: Sat, 1 Feb 2014 21:52:07 +0000 [thread overview]
Message-ID: <CAPM58ogTScy9j_StuTVwY6_xEiD27mi4=t8_kwJcBbOCuVpxZw@mail.gmail.com> (raw)
In-Reply-To: <CAPM58ojZWBFoNv43kxKhqgthcx-z9_d2k+Q4jgN31WODtLX+Tw@mail.gmail.com>
>> > From: Richard Copley <rcopley@gmail.com>
>> > Perhaps some problem with type-punning LARGE_INTEGER/ULARGE_INTEGER under
>> > -fstrict-aliasing [...] I admit it doesn't seem very likely [...]
Impossible, actually, because LARGE_INTEGER and ULARGE_INTEGER are
"compatible types" for the purposes of the strict aliasing rules, as
they differ only in signedness
(http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html#compatible_type).
Nonetheless those casts in Ffile_system_info seem gratuitous.
On 1 February 2014 20:43, Richard Copley <rcopley@gmail.com> wrote:
>On 1 February 2014 20:12, Eli Zaretskii <eliz@gnu.org> wrote:
>> Please try the latest trunk and see if its solves the problem.
> Seems fixed, many thanks. I should rebuild with the libraries enabled to be sure. I will let you know the result.
Yes, still fixed. Thanks again.
next prev parent reply other threads:[~2014-02-01 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 17:32 bug#16615: 24.3.50; Fatal error visiting a directory (same as #16132?) Richard Copley
2014-02-01 18:11 ` Eli Zaretskii
2014-02-01 19:09 ` Richard Copley
2014-02-01 19:34 ` Richard Copley
2014-02-01 20:05 ` Richard Copley
2014-02-01 20:12 ` Eli Zaretskii
2014-02-01 20:43 ` Richard Copley
2014-02-01 21:52 ` Richard Copley [this message]
2014-02-02 3:41 ` Eli Zaretskii
2014-02-01 22:48 ` Juanma Barranquero
2014-02-01 23:03 ` Richard Copley
2014-02-01 23:18 ` Juanma Barranquero
2014-02-01 23:24 ` Richard Copley
2014-02-01 23:33 ` Juanma Barranquero
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='CAPM58ogTScy9j_StuTVwY6_xEiD27mi4=t8_kwJcBbOCuVpxZw@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=16615@debbugs.gnu.org \
--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 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).