From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: 41077@debbugs.gnu.org
Subject: bug#41077: [feature/native-comp] Segfaults when compiling ELC+ELN
Date: Mon, 04 May 2020 23:05:03 +0200 [thread overview]
Message-ID: <87d07jfm2o.fsf@gmail.com> (raw)
In-Reply-To: <xjfy2q7k6fh.fsf@sdf.org> (Andrea Corallo's message of "Mon, 04 May 2020 16:31:46 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> please try compiling and running this:
>
> https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html
>
> we'll know to begin with if this is an issue of the native-comp branch
> or (as I suspect) of the libgccjit package of the distro.
Good guess: that compiles without any warning, then segfaults too.
Should I follow the instructions from
https://gcc.gnu.org/wiki/JIT#Building_it_from_source to get a more
recent libgccjit.so? Is there a minimal required version, or does the
problem come from something else? (E.g. the way the distro compiled the
library.)
Feel free to close this report; I can open a new one if needed after I
get the tutorial you mentioned running correctly.
Thank you for taking a look at this.
next prev parent reply other threads:[~2020-05-04 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:08 bug#41077: [feature/native-comp] Segfaults when compiling ELC+ELN Kévin Le Gouguec
2020-05-04 16:31 ` Andrea Corallo
2020-05-04 20:57 ` Andrea Corallo
2020-05-04 21:05 ` Kévin Le Gouguec [this message]
2020-05-04 21:15 ` Andrea Corallo
2020-05-06 14:15 ` bug#41077: [feature/native-comp] virtual memory exhausted (was: bug#41077: [feature/native-comp] Segfaults when compiling ELC+ELN) Kévin Le Gouguec
[not found] ` <xjfftcd5chc.fsf@sdf.org>
2020-05-06 20:12 ` bug#41077: [feature/native-comp] virtual memory exhausted Andrea Corallo
2020-05-10 14:26 ` Kévin Le Gouguec
2020-05-10 15:02 ` Andrea Corallo
2020-05-10 22:04 ` Kévin Le Gouguec
2020-05-10 22:17 ` Andrea Corallo
2020-05-11 9:12 ` Kévin Le Gouguec
2020-05-11 10:00 ` Andrea Corallo
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=87d07jfm2o.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=41077@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).