unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65640@debbugs.gnu.org, StrawberryTea <look@strawberrytea.xyz>
Subject: bug#65640: 30.0.50; segfault when building emacs with native-comp
Date: Thu, 31 Aug 2023 03:24:34 -0400	[thread overview]
Message-ID: <yp1cyz33c99.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <837cpbg47b.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 31 Aug 2023 08:40:08 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: StrawberryTea <look@strawberrytea.xyz>
>> Date: Wed, 30 Aug 2023 14:38:55 -0500
>> 
>> 
>> Hi. I just set up a fresh install of Gentoo with Clang as my default
>> compiler. At first, I was trying to compile Emacs with Clang and Emacs
>> was finding -lgccjit but not finding the libgccjit.h header file. So I
>> overwrote the compiler Emacs was using to GCC instead and now it
>> compiles but segfaults when native-compiling some Elisp files.
>> 
>> Build log with Clang (configure error): https://bpa.st/ODFBK
>> Build log with GCC (segfault): https://0x0.st/Hpbz.txt
>
> First, you apply local patches to the Emacs tree, so you are compiling
> code that is not from our Git repository, but some variation of that.
>
> More importantly: it looks like you build Emacs with "-O3 -march=native",
> which are not the default compilation switches, and cause GCC to
> over-optimize the code.  Please try again without those switches.
>
> If using the default compiler switches doesn't help, please run the
> crashing command under GDB, and when it segfaults, produce the
> C-level backtrace and post it here.
>
> Please also always post the build logs as plain text or attachments to
> your messages, instead of pointing to a URL that could some day go
> away, and thus years from now people will be unable to see the log by
> reading this discussion.
>
> Thanks.
>
> P.S. Adding Andrea.

Agree on everything, from this far (and for whatever reason) looks like
the crash is in libgccjit.  So its version might be relevant as well.

Thanks

  Andrea





  reply	other threads:[~2023-08-31  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 19:38 bug#65640: 30.0.50; segfault when building emacs with native-comp StrawberryTea
2023-08-31  5:40 ` Eli Zaretskii
2023-08-31  7:24   ` Andrea Corallo [this message]
2023-09-01 15:05     ` LemonBreezes
2023-09-01 15:28       ` Eli Zaretskii
     [not found]         ` <0d10be97-ac8a-48b7-887e-1e9ae169daf2@app.fastmail.com>
2023-09-01 17:27           ` Eli Zaretskii
2023-09-01 20:48             ` LemonBreezes
2023-09-01 20:57               ` Stefan Kangas

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=yp1cyz33c99.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=65640@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=look@strawberrytea.xyz \
    /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).