unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mark A. Hershberger" <mah@nichework.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: "Mark A. Hershberger" <mah@everybody.org>, 45056@debbugs.gnu.org
Subject: bug#45056: 28.0.50; lexical-let doesn't work with returned closures on nativecomp
Date: Sat, 5 Dec 2020 13:57:21 -0800 (PST)	[thread overview]
Message-ID: <1009119049.161679.1607205441220.JavaMail.zimbra@nichework.com> (raw)
In-Reply-To: <216496280.161579.1607203268073.JavaMail.zimbra@nichework.com>


On Dec 5, 2020, at 4:21 PM, Mark A. Hershberger mah@nichework.com wrote:

>> have you checked if this behavior is common to the non native build?
> 
> I can compile a non-native build and verify that the problem goes away.  I'll
> report back when it is done.

Compiled a non-native emacs and it did not exhibit this bug.

In GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0)
 of 2020-12-05 built on silk
Repository revision: fc54c835181eb88a748d2fd49b7a4c78b9fe82ee
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12004000
System Description: Debian GNU/Linux 10 (buster)

Configured using:
 'configure --with-modules --with-xwidgets --with-gconf --with-cairo
 --with-json --with-nativecomp --with-imagemagick'

Configured features:
XPM JPEG TIFF GIF PNG RSVG CAIRO IMAGEMAGICK SOUND GPM DBUS GCONF
GSETTINGS GLIB NOTIFY INOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE
HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM
MODULES THREADS XWIDGETS LIBSYSTEMD JSON PDUMPER LCMS2

(Note that my compilation script used --with-nativecomp but, since it is using
master instead of the nativecomp branch, NATIVE_COMP is missing from the
"Configured features" list.)





  reply	other threads:[~2020-12-05 21:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 18:16 bug#45056: 28.0.50; lexical-let doesn't work with returned closures on nativecomp Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-05 19:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-05 21:21   ` Mark A. Hershberger
2020-12-05 21:57     ` Mark A. Hershberger [this message]
2020-12-05 22:06       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-06  0:26         ` Mark A. Hershberger
2020-12-06 10:33           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-06 19:55             ` Mark A. Hershberger
2020-12-07 15:45               ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 14:59                 ` Mark A. Hershberger
2020-12-08 15:18                   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 20:45                     ` Mark A. Hershberger
2020-12-08 21:28                       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 21:42                         ` Mark A. Hershberger
2020-12-08 22:21                           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-29 22:06                             ` Mark A. Hershberger

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=1009119049.161679.1607205441220.JavaMail.zimbra@nichework.com \
    --to=mah@nichework.com \
    --cc=45056@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=mah@everybody.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).