From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jean Louis <bugs@gnu.support>
Cc: 44014@debbugs.gnu.org
Subject: bug#44014: 28.0.50; Incorrect compilter warning that function is called with 2 arguments
Date: Thu, 15 Oct 2020 18:34:10 +0200 [thread overview]
Message-ID: <87362fv471.fsf@gnus.org> (raw)
In-Reply-To: <20201015133426.GB20257@protected.rcdrun.com> (Jean Louis's message of "Thu, 15 Oct 2020 16:34:26 +0300")
Jean Louis <bugs@gnu.support> writes:
> Thanks. Compiler warning shows different line number, is that normal?
Here's a minimal case to reproduce the bug:
(defun bar (a)
a)
(defun foo ()
(bar 1)
(bar 1 2)
(bar 1))
It'll say that the error is on the final call to bar, not the preceding
line. If I remove the first call to bar, then it puts the error on the
correct line.
Anybody know what could be causing this bug?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-15 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 13:24 bug#44014: 28.0.50; Incorrect compilter warning that function is called with 2 arguments Jean Louis
2020-10-15 13:31 ` Lars Ingebrigtsen
2020-10-15 13:34 ` Jean Louis
2020-10-15 16:34 ` Lars Ingebrigtsen [this message]
2020-10-15 16:52 ` Eli Zaretskii
2020-10-15 17:25 ` Jean Louis
2022-01-28 15:19 ` bug#44014: Byte-compile warnings on the wrong line Lars Ingebrigtsen
[not found] ` <handler.44014.B.160276832222300.ack@debbugs.gnu.org>
2020-10-15 13:32 ` bug#44014: Acknowledgement (28.0.50; Incorrect compiler warning that function is called with 2 arguments) Jean Louis
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=87362fv471.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44014@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).