unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45858@debbugs.gnu.org
Subject: bug#45858: 28.0.50; [native-comp] compilation very slow
Date: Sun, 31 Jan 2021 03:54:54 +0100	[thread overview]
Message-ID: <877dnt3jep.fsf@telefonica.net> (raw)
In-Reply-To: <xjf4kj0wyfs.fsf@sdf.org> (Andrea Corallo's message of "Thu, 28 Jan 2021 21:20:39 +0000")

Andrea Corallo <akrl@sdf.org> writes:

> This is behaviour is unexpected, but is kind of hard if not impossible
> to guess the issue from here.
>
> I guess both Emacs and and libgccjit are not debug build correct?

The build was performed with

../emacs/configure --without-toolkit-scroll-bars --with-x-toolkit=lucid --with-modules --without-imagemagick --with-nativecomp && make -j8

libgccjit was installed from Debian's package (gcc 10.2.1-6):

lrwxrwxrwx 1 root root       40 ene 10 12:35 /usr/lib/gcc/x86_64-linux-gnu/10/libgccjit.so -> ../../../x86_64-linux-gnu/libgccjit.so.0
lrwxrwxrwx 1 root root       18 ene 10 12:35 /usr/lib/x86_64-linux-gnu/libgccjit.so.0 -> libgccjit.so.0.0.1
-rw-r--r-- 1 root root 26103760 ene 10 12:35 /usr/lib/x86_64-linux-gnu/libgccjit.so.0.0.1

Even supposing that libgccjit was built by mistake on debug mode, I
guess that it would not take so much time to compile an .eln.

I'll try building gccemacs from a pristine checkout on a few days. Let's
see if the problem persists.





  reply	other threads:[~2021-01-31  2:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 12:24 bug#45858: 28.0.50; [native-comp] compilation very slow Óscar Fuentes
2021-01-28 21:20 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-31  2:54   ` Óscar Fuentes [this message]
2021-02-02 22:13     ` Óscar Fuentes

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=877dnt3jep.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=45858@debbugs.gnu.org \
    --cc=akrl@sdf.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).