From: Sven Hartrumpf <hartrumpf@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 28.1 built with x32 ABI outperforms x86-64
Date: Sun, 10 Apr 2022 08:02:52 +0200 (CEST) [thread overview]
Message-ID: <20220410.080252.204270088.hartrumpf@gmx.net> (raw)
In-Reply-To: <874k33trz8.fsf@zoho.eu>
Hello.
Emanuel wrote, 2022-04-08 19:17:
> Sven wrote:
> Yes, can you post the script (or function) that carried out
> the experiment?
Sure, see below.
Some notes:
- gccx32 is a tiny script that calls gcc in x32 mode
(just passing CFLAGS to configure does not work as expected), containing:
gcc-11 -mx32 -I/usr/local/include/x86_64-linux-gnux32 -I/usr/x86_64-linux-gnux32/include "$@"
- dropcaches-root is s tool that avoids filesystem cache effects, simlar to a:
echo 3 > /proc/sys/vm/drop_caches
- I call the script emacs.install as follows:
emacs.install x86-64 |& tee emacs.64
emacs.install x32 |& tee emacs.x32
To test the second line, you will need all the x32 builds that I mentioned in my first mail.
--- emacs.install
#!/bin/bash
set -e -u -x
ABI=$1
tar xf emacs-28.1.tar.gz
cd emacs-28.1
if [ "$ABI" == "x32" ] ; then
CC=gccx32 ./configure --prefix=/usr/local --bindir=/usr/local/binx32 --includedir=/usr/local/includex32 --libdir=/usr/local/libx32 --with-sound=no --without-dbus --without-x
else # normal 64 bit
CC=gcc-11 ./configure --prefix=/usr/local --bindir=/usr/local/bin64 --libdir=/usr/local/lib64 --with-sound=no --without-dbus --without-x
fi
make -j4
strip src/emacs
dropcaches-root
date -Is
make check
find lisp -name '*.elc' | grep -v -e '/c-by.elc$' -e 'bindat.elc' | xargs rm # grep to avoid 2 files where compilation fails with max-lisp-eval-depth error
date -Is
make
date -Is
---
prev parent reply other threads:[~2022-04-10 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:50 Emacs 28.1 built with x32 ABI outperforms x86-64 Sven Hartrumpf
2022-04-08 17:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-04-10 6:02 ` Sven Hartrumpf [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=20220410.080252.204270088.hartrumpf@gmx.net \
--to=hartrumpf@gmx.net \
--cc=help-gnu-emacs@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.
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).