From: "Alex Bennée" <alex.bennee@linaro.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrea Corallo <akrl@sdf.org>, 48097@debbugs.gnu.org
Subject: bug#48097:
Date: Thu, 29 Apr 2021 15:31:14 +0100 [thread overview]
Message-ID: <CAHDbmO2sFnJ4PvKi3w0+HugSUVcWnSct-5fFAqB2K209gLZHDA@mail.gmail.com> (raw)
In-Reply-To: <838s51dyl6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
During my rebuild I did a distclean, wiped the old install directory and
also cleared the eln-cache just to make sure everything was pristine. The
function in question is reported as natively compiled:
c-determine-limit-no-macro is a native compiled Lisp function in
‘cc-engine.el’.
On Thu, 29 Apr 2021 at 14:12, Eli Zaretskii <eliz@gnu.org> wrote:
> > Cc: 48097@debbugs.gnu.org
> > Date: Thu, 29 Apr 2021 12:17:43 +0000
> > From: Andrea Corallo via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >
> > Alex Bennée <alex.bennee@linaro.org> writes:
> >
> > > I suspect this might be a duplicate of #48061 - re-building with the
> current master the bug has gone away and problems
> > > with c-mode cause by strange code would certainly explain it.
> >
> > Hi Alex,
> >
> > okay shall we close this then?
>
> Please don't close yet, I still see the problem.
>
> It is strange that Alex says bug#48061 should solve this: the fix for
> that bug changed comp-cstr.el, and I have that natively-compiled after
> that change. Do I need to make sure other files are recompiled, for
> example the CC mode files?
>
--
Alex Bennée
KVM/QEMU Hacker for Linaro
[-- Attachment #2: Type: text/html, Size: 1906 bytes --]
next prev parent reply other threads:[~2021-04-29 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:14 bug#48097: 28.0.50; C code not being correctly fontified in features/native-comp Alex Bennée
2021-04-29 10:34 ` bug#48097: Alex Bennée
2021-04-29 12:17 ` bug#48097: Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 12:21 ` bug#48097: Alex Bennée
2021-04-29 13:12 ` bug#48097: Eli Zaretskii
2021-04-29 14:26 ` bug#48097: Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 15:00 ` bug#48097: Eli Zaretskii
2021-04-29 14:31 ` Alex Bennée [this message]
2021-04-29 12:28 ` bug#48097: Eli Zaretskii
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=CAHDbmO2sFnJ4PvKi3w0+HugSUVcWnSct-5fFAqB2K209gLZHDA@mail.gmail.com \
--to=alex.bennee@linaro.org \
--cc=48097@debbugs.gnu.org \
--cc=akrl@sdf.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).