From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: gazally@runbox.com,
bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org,
schwab@linux-m68k.org, npostavs@gmail.com, 31688@debbugs.gnu.org
Subject: bug#31688: 26.1.50; Byte compiler confuses two string variables
Date: Mon, 04 Jun 2018 18:58:19 +0300 [thread overview]
Message-ID: <83zi0abl2c.fsf@gnu.org> (raw)
In-Reply-To: <2a9f684c2867ae9a7deccb51d04f9de6@webmail.orcon.net.nz> (message from Phil Sainty on Mon, 04 Jun 2018 22:02:27 +1200)
> Date: Mon, 04 Jun 2018 22:02:27 +1200
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: Gemini Lasswell <gazally@runbox.com>, Noam Postavsky <npostavs@gmail.com>,
> bug-gnu-emacs <bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org>,
> 31688@debbugs.gnu.org
>
> Again, it bothers me to think that someone could observe a bug when
> running byte-compiled code, and try to debug it but, through the
> process of instrumenting functions for debugging, unwittingly change
> the behaviour of the code such that the bug no longer occurs.
Byte compilation includes optimizations, and the fact that optimized
code can behave differently from unoptimized one is well known in
every programming language. When you get differences, you have code
that relies on undefined behavior, which I believe is the point
Andreas was making.
next prev parent reply other threads:[~2018-06-04 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 17:51 bug#31688: 26.1.50; Byte compiler confuses two string variables Gemini Lasswell
2018-06-02 18:02 ` Noam Postavsky
2018-06-02 22:52 ` Gemini Lasswell
2018-06-02 23:25 ` Noam Postavsky
2018-06-03 0:40 ` Drew Adams
2018-06-02 23:03 ` Drew Adams
2018-06-02 23:38 ` Phil Sainty
2018-06-02 23:54 ` Noam Postavsky
2018-06-03 12:32 ` Phil Sainty
2018-06-03 13:05 ` Andreas Schwab
2018-06-04 10:02 ` Phil Sainty
2018-06-04 15:58 ` Eli Zaretskii [this message]
2018-06-04 17:01 ` Andreas Schwab
2018-06-08 15:09 ` Eli Zaretskii
2018-06-03 0:02 ` Michael Heerdegen
2018-06-03 0:46 ` Drew Adams
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=83zi0abl2c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31688@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org \
--cc=gazally@runbox.com \
--cc=npostavs@gmail.com \
--cc=psainty@orcon.net.nz \
--cc=schwab@linux-m68k.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).