From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 26597@debbugs.gnu.org
Subject: bug#26597: 25.1; Compilation error on master with --enable-check-lisp-object-type
Date: Mon, 01 May 2017 08:20:26 -0400 [thread overview]
Message-ID: <jwvmvawn5af.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: <m2shl134rd.fsf@gmail.com>
> Replacing a primitive value with a struct containing such a value
> should never degrade performance; that would be a compiler bug.
FWIW, No, compilers do not guarantee that semantically-equivalent
programs will be compiled to code with equivalent performance, so it
wouldn't be a bug. It's only a "quality of implementation" issue.
Stefan
next prev parent reply other threads:[~2017-05-01 12:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 20:05 bug#26597: 25.1; Compilation error on master with --enable-check-lisp-object-type Philipp Stephani
2017-04-22 7:42 ` Eli Zaretskii
2017-04-22 11:57 ` Philipp Stephani
2017-04-22 13:35 ` Andreas Schwab
2017-05-01 11:26 ` Philipp Stephani
2017-04-22 13:36 ` Eli Zaretskii
2017-05-01 11:32 ` Enabling --enable-check-lisp-object-type by default on x86 and AMD64 (was: Re: bug#26597: 25.1; Compilation error on master with --enable-check-lisp-object-type) Philipp Stephani
2017-05-02 22:14 ` Enabling --enable-check-lisp-object-type by default on x86 and AMD64 Paul Eggert
2017-05-03 2:38 ` Eli Zaretskii
2017-05-03 3:24 ` Paul Eggert
2017-05-03 14:48 ` Eli Zaretskii
2017-05-03 18:08 ` Paul Eggert
2017-05-03 18:22 ` Eli Zaretskii
2017-05-04 14:33 ` Eli Zaretskii
2017-05-05 23:23 ` Paul Eggert
2017-05-06 7:07 ` Eli Zaretskii
2017-05-06 23:23 ` Paul Eggert
2017-05-01 12:20 ` Stefan Monnier [this message]
2017-05-01 14:33 ` bug#26597: 25.1; Compilation error on master with --enable-check-lisp-object-type Philipp Stephani
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvmvawn5af.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=26597@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.