From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63365@debbugs.gnu.org, akrl@sdf.org
Subject: bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation
Date: Thu, 01 Feb 2024 12:11:25 +0100 [thread overview]
Message-ID: <861q9wigma.fsf@gnu.org> (raw)
In-Reply-To: <86o7d0zbtu.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 01 Feb 2024 13:02:53 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Does this mean the build of the master branch still crashes for you?
> I thought this was resolved long ago... Or do you work around this in
> some way?
It did crash during this build, yes. The solution provided once was to
set '-fno-optimize-sibling-calls', and this is what I usually do and it
works:
$ CFLAGS='-O2 -fno-optimize-sibling-calls' ./configure ...
> Thanks. I think this means the problem with the backtrace addresses
> has been solved, indeed: the frames which are printed with file name
> and function name looks reasonable. Those which remained "??" I think
> are due to optimizations or something. It would be educational to see
> a corresponding backtrace from GDB, if you can capture it, since we
> will be able then to compare the "??" portions with what GDB knows
> about them.
Did you give me a recipe how to produce the backtrace from GDB?
Otherwise I'll go through this thread and look.
Best, Arash
next prev parent reply other threads:[~2024-02-01 11:11 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 8:16 bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation Arash Esbati
2023-05-08 11:48 ` Eli Zaretskii
2023-05-08 14:36 ` Arash Esbati
2023-05-08 15:13 ` Eli Zaretskii
2023-05-08 19:34 ` Arash Esbati
2023-05-09 5:05 ` Eli Zaretskii
2023-05-09 12:12 ` Arash Esbati
2023-05-09 12:49 ` Eli Zaretskii
2023-05-10 12:37 ` Arash Esbati
2023-05-10 12:48 ` Eli Zaretskii
2023-05-10 14:27 ` Arash Esbati
2023-05-10 16:54 ` Eli Zaretskii
2023-05-10 19:08 ` Eli Zaretskii
2023-05-11 10:06 ` Eli Zaretskii
2024-01-26 13:11 ` Eli Zaretskii
2024-01-26 18:24 ` Arash Esbati
2024-01-26 18:59 ` Eli Zaretskii
2024-01-26 20:33 ` Arash Esbati
2024-02-01 10:39 ` Arash Esbati
2024-02-01 11:02 ` Eli Zaretskii
2024-02-01 11:11 ` Arash Esbati [this message]
2024-02-01 11:27 ` Eli Zaretskii
2023-05-26 13:05 ` Arash Esbati
2023-05-26 13:42 ` Eli Zaretskii
2023-05-26 19:21 ` Arash Esbati
2023-05-27 6:00 ` Eli Zaretskii
2023-05-27 10:57 ` Arash Esbati
2023-05-27 11:33 ` Eli Zaretskii
2023-05-27 17:35 ` Arash Esbati
2023-05-28 6:55 ` Eli Zaretskii
2023-06-01 7:31 ` András Svraka
2023-06-01 7:37 ` András Svraka
2023-06-01 8:42 ` Eli Zaretskii
2023-06-01 8:49 ` Andrea Corallo
2023-06-01 15:33 ` András Svraka
2023-06-01 15:30 ` András Svraka
2023-06-01 16:25 ` Eli Zaretskii
2023-06-08 10:21 ` Arash Esbati
2023-06-08 13:19 ` Eli Zaretskii
2023-06-08 14:02 ` Andrea Corallo
2023-06-08 14:18 ` Eli Zaretskii
2023-06-08 14:39 ` Andrea Corallo
2023-06-08 22:08 ` Arash Esbati
2023-06-08 22:27 ` Arash Esbati
2023-06-16 9:04 ` Cyril Arnould
2023-06-16 10:31 ` Eli Zaretskii
2023-06-16 14:49 ` Andrea Corallo
2023-06-16 14:52 ` Andrea Corallo
2023-06-22 20:34 ` Arash Esbati
2023-06-23 5:32 ` Eli Zaretskii
2023-06-23 11:41 ` Arash Esbati
2023-06-23 12:15 ` Eli Zaretskii
2023-06-23 12:50 ` Arash Esbati
2023-06-24 9:17 ` Deus Max
2023-06-24 9:21 ` Eli Zaretskii
2023-06-24 14:41 ` Deus Max
2023-06-24 15:05 ` Eli Zaretskii
2023-06-25 13:51 ` Andrea Corallo
2023-06-25 15:41 ` Eli Zaretskii
2023-06-25 18:11 ` Andrea Corallo
2023-06-25 18:31 ` Eli Zaretskii
2023-06-26 7:03 ` Andrea Corallo
2023-06-26 22:04 ` Cyril Arnould
2023-06-27 2:30 ` Eli Zaretskii
2023-06-27 19:28 ` Cyril Arnould
2023-06-27 20:22 ` Andrea Corallo
2024-05-14 19:52 ` Cyril Arnould
2024-05-14 20:33 ` bug#63365: bug#65727: 30.0.50; Build failure in MSYS2 when --with-native-compilation Andrea Corallo
2024-05-14 23:29 ` Cyril Arnould
2024-05-15 6:38 ` Andrea Corallo
2024-05-15 16:35 ` Cyril Arnould
2024-05-15 17:09 ` bug#63365: " Andrea Corallo
2024-05-15 18:45 ` Cyril Arnould
2024-05-16 13:59 ` bug#63365: " Andrea Corallo
2024-05-16 20:08 ` Cyril Arnould
2024-05-17 4:42 ` Andrea Corallo
2024-05-17 12:06 ` Andrea Corallo
2024-05-17 13:03 ` bug#65727: " Eli Zaretskii
2024-05-17 17:28 ` Andrea Corallo
2024-05-18 7:09 ` bug#63365: " Andrea Corallo
2024-05-18 9:53 ` Cyril Arnould
2024-05-18 17:30 ` bug#63365: " Andrea Corallo
2023-06-28 11:37 ` bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation Eli Zaretskii
2023-06-28 23:16 ` Cyril Arnould
2023-06-29 5:20 ` Eli Zaretskii
2023-06-29 6:36 ` Cyril Arnould
2023-06-29 8:21 ` Andrea Corallo
2023-06-29 9:16 ` bug#63365: AW: " Cyril Arnould
[not found] <AS4PR10MB6110F1445D9658E48521DDD2E358A@AS4PR10MB6110.EURPRD10.PROD.OUTLOOK.COM>
2023-06-20 8:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861q9wigma.fsf@gnu.org \
--to=arash@gnu.org \
--cc=63365@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@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.