From: Pip Cet <pipcet@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: Erik Hetzner <egh@e6h.org>, 46974-done@debbugs.gnu.org
Subject: bug#46974: 28.0.50; [nativecomp] wrong-type-argument number-or-marker-p with native compiled code only
Date: Sun, 7 Mar 2021 20:43:11 +0000 [thread overview]
Message-ID: <CAOqdjBc1cMfxKPRdB=DbXr27OG9k+9=-TWi017V5hnB42QFYng@mail.gmail.com> (raw)
In-Reply-To: <xjfo8fuzotm.fsf@sdf.org>
On Sun, Mar 7, 2021 at 8:33 PM Andrea Corallo <akrl@sdf.org> wrote:
> Pip Cet <pipcet@gmail.com> writes:
> > Perfectly open question: how would you feel about adding LAP
> > reproducers for cases like this one, where it's hard to get at the
> > Lisp source? I think I've got the reproducer LAP code here, and it
> > shouldn't be too hard to write comp--native-compile-lap, but if you'd
> > prefer not to go that way I'm perfectly okay with it, too.
>
> I'm open to the idea of having a new way to stress the code in the
> testsuite, I'm a little doubtful this worth of, well certainly for this
> specific case where the patch is clearly correct.
>
> What's your feeling about this?
I think this is going to be something we want eventually, but it's
harder than I thought, so I won't pursue this for now.
Pip
next prev parent reply other threads:[~2021-03-07 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 19:21 bug#46974: 28.0.50; [nativecomp] wrong-type-argument number-or-marker-p with native compiled code only Erik Hetzner
2021-03-06 20:28 ` Pip Cet
2021-03-06 20:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-07 3:24 ` Erik Hetzner
2021-03-07 6:30 ` Pip Cet
2021-03-07 19:41 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-07 20:13 ` Pip Cet
2021-03-07 20:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-07 20:43 ` Pip Cet [this message]
2021-03-07 20:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CAOqdjBc1cMfxKPRdB=DbXr27OG9k+9=-TWi017V5hnB42QFYng@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=46974-done@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=egh@e6h.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).