[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilati
From: |
Andrea Corallo |
Subject: |
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation |
Date: |
Mon, 26 Jun 2023 03:03:32 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: arash@gnu.org, cyril.arnould@outlook.com, 63365@debbugs.gnu.org,
>> svraka.andras@gmail.com
>> Date: Sun, 25 Jun 2023 14:11:15 -0400
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> Maybe someone should compare the two binaries (with and without
>> >> -foptimize-sibling-calls) to understand which compilation unit (and
>> >> which function) differs in details.
>> >
>> > How does one compare binaries in a useful way? The Emacs binary is
>> > AFAIR around 20MB even when stripped of all symbols.
>>
>> That's a good question, for elf there are specific tools for that, even
>> just readelf can output function sizes and that's a good starting point.
>>
>> For Windows I've idea (I'm assuming Windows is not elf based).
>
> No, Windows doesn't use ELF.
>
> Maybe we should start by narrowing the problem? E.g., which Lisp
> files cause the crashes, and which *.eln files, if any, are involved?
>
> The C files more or less directly involved in byte-compilation are, I
> think, eval.c, data.c, alloc.c, lread.c, bytecode.c. If we think one
> of these could be involved, it would be nice to find the one(s) that
> cause the problem, for example, by selectively compiling only those
> with -fno-optimize-sibling-calls, then removing them one by one from
> the set of files compiled like that.
That would be a good starting point already, I'd suggest to add comp.c
to the investigated set as well.
Thanks
Andrea
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, (continued)
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Eli Zaretskii, 2023/06/23
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Arash Esbati, 2023/06/23
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Deus Max, 2023/06/24
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Eli Zaretskii, 2023/06/24
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Deus Max, 2023/06/24
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Eli Zaretskii, 2023/06/24
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Andrea Corallo, 2023/06/25
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Eli Zaretskii, 2023/06/25
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Andrea Corallo, 2023/06/25
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Eli Zaretskii, 2023/06/25
- bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation,
Andrea Corallo <=
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Cyril Arnould, 2023/06/17
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Cyril Arnould, 2023/06/26
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Cyril Arnould, 2023/06/27
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Cyril Arnould, 2023/06/28
bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation, Cyril Arnould, 2023/06/29