From: Eli Zaretskii <eliz@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: Warnings: Native VS Byte Compiler
Date: Thu, 06 May 2021 07:55:10 +0300 [thread overview]
Message-ID: <835yzwfolt.fsf@gnu.org> (raw)
In-Reply-To: <20210505214501.CE6A9C217FD@raman-glaptop.localdomain>
> From: "T.V Raman" <raman@google.com>
> Date: Wed, 5 May 2021 14:45:01 -0700 (PDT)
>
> I notice in the *warnings* buffer after starting with native-comp
> enabled:
>
> Warnings that dont show up when using byte compilation examples
> include constructor functions generated by cl-defstruct for instance.
This is a known issue.
> Would be good to make spurious warnings go away so one can focus on
> the real ones; native compilation may well be catching things that are
> not always defined at the right time and fixing those may well be
> benefitial from a package-author standpoint.
They aren't spurious warnings, they are real warnings about real
problems in our Lisp code. It's just that native compilation catches
more of them. We should fix all of them. So please report each such
warning as a bug.
prev parent reply other threads:[~2021-05-06 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 21:45 Warnings: Native VS Byte Compiler T.V Raman
2021-05-06 4:55 ` Eli Zaretskii [this message]
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=835yzwfolt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
/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).