From: "Mike Z.Vand" <email@example.com>
To: "firstname.lastname@example.org" <email@example.com>
Subject: [musl] Reverting a GCC bug workaround commit from 8 years ago
Date: Tue, 12 Jul 2022 23:55:07 +0000 (UTC) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
I was following down a rabbit hole, investigating a weird WebAssembly code generation from wasi-libc, when I saw these strange volatile attributes for some pointers in stdio source code. As it happens, it was a GCC bug workaround that was introduced around 8 years ago (commit a6adb2bcd8145353943377d6119c1d7a4242bae1 work around constant folding bug 61144 in gcc 4.9.0 and 4.9.1).
As comment explained this commit could be "reconsidered and possibly reverted at some point in the future when the broken gcc versions are no longer relevant".
I very much hope it is the time we can revert this and give the compiler more wiggle room to do its thing and have less volatile keywords here and there for healthier looking code overall.
Thank you so much for all the work that has been done on musl.Mike
[-- Attachment #2: Type: text/html, Size: 1872 bytes --]
next parent reply other threads:[~2022-07-13 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2022-07-12 23:55 ` Mike Z.Vand [this message]
2022-07-13 1:22 ` Rich Felker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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 NNTP newsgroup(s).