From: Alan Mackenzie <acm@muc.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Eli Zaretskii" <eliz@gnu.org>,
61962@debbugs.gnu.org
Subject: bug#61962: 30.0.50; New trouble with symbols with positions
Date: Sun, 5 Mar 2023 18:39:05 +0000 [thread overview]
Message-ID: <ZAThyXeTjgfCwwka@ACM> (raw)
In-Reply-To: <877cvvqj5v.fsf@web.de>
Hello, Michael.
On Sun, Mar 05, 2023 at 17:04:12 +0100, Michael Heerdegen wrote:
> Mattias Engdegård <mattiase@acm.org> writes:
> > That would very likely be fcf2f7aead.
> When this issue is not easy to fix, ....
I will look into this in the next day or two.
> .... maybe consider to revert that commit for now (inexact compiler
> warning positions are less problematic than breaking Elisp code).
I disagree with your concept here. Warning positions are not accurate
or inaccurate (they cannot be +- 2%, for example), they are either
correct or they are wrong. A lot of effort was put into making them
correct, although it is clear from this bug that that project is as yet
incomplete.
Please don't revert that commit from 2023-02-17. I will look into this
and try to fix the bug properly.
> Michael.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-03-05 18:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 16:18 bug#61962: 30.0.50; New trouble with symbols with positions Michael Heerdegen
2023-03-04 16:34 ` Eli Zaretskii
2023-03-04 21:39 ` Mattias Engdegård
2023-03-04 21:53 ` Michael Heerdegen
2023-03-05 16:04 ` Michael Heerdegen
2023-03-05 18:39 ` Alan Mackenzie [this message]
2023-03-05 19:41 ` Michael Heerdegen
2023-03-06 13:22 ` Alan Mackenzie
2023-03-07 0:29 ` Michael Heerdegen
2023-03-07 10:24 ` Alan Mackenzie
2023-03-07 13:13 ` Eli Zaretskii
2023-03-07 13:51 ` Robert Pluim
2023-03-07 15:46 ` Alan Mackenzie
2023-03-12 17:30 ` Mattias Engdegård
2023-03-12 20:42 ` Alan Mackenzie
2023-03-13 14:50 ` Eli Zaretskii
2023-03-14 12:31 ` Mattias Engdegård
2023-03-07 15:42 ` Alan Mackenzie
2023-03-07 15:15 ` Michael Heerdegen
2023-03-04 16:36 ` Eli Zaretskii
2023-03-04 16:47 ` Michael Heerdegen
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=ZAThyXeTjgfCwwka@ACM \
--to=acm@muc.de \
--cc=61962@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
--cc=michael_heerdegen@web.de \
/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).