public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jose.marchesi at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/25521] change semantics of const volatile variables Date: Wed, 03 Aug 2022 18:21:04 +0000 [thread overview] Message-ID: <bug-25521-4-2lIQDY0DtD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-25521-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25521 --- Comment #9 from Jose E. Marchesi <jose.marchesi at oracle dot com> --- So I got feedback from the clang/llvm folks on this. As you can see in [1] they asked the WG14 reflectors about the footnote 135 in the C18 spec and their conclusion is that there is no normative objection to place `const volatile' variables in read-only sections, much like non-volatile consts. This matches my earlier impression (before I got pointed to that footnote) and since there is at least one target being impacted by this GCC/LLVM discrepancy (bpf-unknown-none) I intend to prepare a patch to change the place where GCC places the `const volatiles'. [1] https://github.com/llvm/llvm-project/issues/56468
next prev parent reply other threads:[~2022-08-03 18:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25521-4@http.gcc.gnu.org/bugzilla/> 2011-12-22 1:16 ` pinskia at gcc dot gnu.org 2011-12-22 1:18 ` pinskia at gcc dot gnu.org 2022-07-10 20:06 ` jose.marchesi at oracle dot com 2022-07-10 20:19 ` jose.marchesi at oracle dot com 2022-07-11 1:53 ` jose.marchesi at oracle dot com 2022-08-03 18:21 ` jose.marchesi at oracle dot com [this message] 2022-09-29 11:14 ` cvs-commit at gcc dot gnu.org 2005-12-21 18:57 [Bug middle-end/25521] New: " drepper at redhat dot com 2005-12-21 19:17 ` [Bug middle-end/25521] " gdr at integrable-solutions dot net 2005-12-21 19:38 ` drepper at redhat dot com 2005-12-21 19:54 ` gdr at integrable-solutions dot net
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=bug-25521-4-2lIQDY0DtD@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).