GNU bug report logs - #35502
27.0.50; encode-time apparently stopped working

Previous Next

Full log

Message #17 received at 35502 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: 35502 <at> debbugs.gnu.org, mbork <at> mbork.pl
Subject: Re: bug#35502: 27.0.50; encode-time apparently stopped working
Date: Tue, 30 Apr 2019 18:43:48 +0300

> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: Marcin Borkowski <mbork <at> mbork.pl>,  35502 <at> debbugs.gnu.org
> Date: Tue, 30 Apr 2019 17:39:32 +0200
> 
>     Eli> I cannot reproduce this with today's master, neither on
>     Eli> GNU/Linux nor on MS-Windows.  Is this in "emacs -Q"?  If so,
>     Eli> what happens if you build a fresh checkout or bootstrap?
> 
>     Eli> Also, what is your version of GCC?
> 
> I see this, but only on macOS, not GNU/Linux:
> 
> Debugger entered--Lisp error: (error "Specified time is not representable")
>   encode-time((29 31 17 30 4 2019 2 t 7200))
> 
> If I change that 't' to 'nil', it works:
> 
>     (encode-time '(29 31 17 30 4 2019 2 nil 7200))
>     (23752 27217)
> 
> $ gcc -v
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 10.0.1 (clang-1001.0.46.4)
> Target: x86_64-apple-darwin18.5.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Is this an optimized build or an unoptimized one?  If the former, can
you try rebuilding with __attribute((cold)) use disabled?  You can do
that in conf_post.h, where ATTRIBUTE_COLD is defined.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.