From: Eli Zaretskii <eliz@gnu.org>
To: Deus Max <deusmax@gmx.com>
Cc: 63365@debbugs.gnu.org, arash@gnu.org, acorallo@gnu.org,
svraka.andras@gmail.com, cyril.arnould@outlook.com
Subject: bug#63365: 30.0.50; GCC 13.1 breaks building Emacs with native-compilation
Date: Sat, 24 Jun 2023 18:05:22 +0300 [thread overview]
Message-ID: <83bkh4zyrx.fsf@gnu.org> (raw)
In-Reply-To: <87fs6gkjmt.fsf@aia00820.aia.gr> (message from Deus Max on Sat, 24 Jun 2023 17:41:30 +0300)
> From: Deus Max <deusmax@gmx.com>
> Cc: Deus Max <deusmax@gmx.com>, arash@gnu.org, 63365@debbugs.gnu.org,
> acorallo@gnu.org, svraka.andras@gmail.com, cyril.arnould@outlook.com
> Date: Sat, 24 Jun 2023 17:41:30 +0300
>
> >> Interesting.
> >> This recommendation and the explanation are worth documenting somewhere.
> >> Shouldn't a new bug be opened on documenting the GCC -O3 recommendation?
> >
> > I don't think it's our business to document this. The default build
> > procedure correctly uses -O2. People who use non-default compilation
> > switches should know what they are doing.
>
> Then whose business is it?
That of the GCC developers, of course. That's where the description
of -O3 and its practical implications belongs.
> The default of course is correct, also it is not intuitive that -O3 is
> wrong. People who...should know what they are doing, but a little
> explanation goes a long way. It also helps newcomers catch up.
Where do you suggest to put these factoids to make them even
marginally discoverable by those for whom you think they will be
useful? If they are hidden among the rest of 100K lines of the ELisp
manual, how will anyone be able to find them?
That is why each piece of documentation should be in its natural
place. When I want to know something about GCC optimization options,
I turn to the GCC manual, nowhere else.
next prev parent reply other threads:[~2023-06-24 15:05 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
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 [this message]
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
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=83bkh4zyrx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63365@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=arash@gnu.org \
--cc=cyril.arnould@outlook.com \
--cc=deusmax@gmx.com \
--cc=svraka.andras@gmail.com \
/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).