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: Sun, 10 Jul 2022 20:19:24 +0000	[thread overview]
Message-ID: <bug-25521-4-XCMOlR2FMO@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 #7 from Jose E. Marchesi <jose.marchesi at oracle dot com> ---
If, as a workaround, I try to use a `section' attribute, like in:

  __attribute__((section(".rodata"))) volatile const int lala = 0;

I don't get an ICE, but a section with write permissions:

  .section        .rodata,"aw"

And the assembler then complains:

  foo-gcc.s:4: Warning: setting incorrect section attributes for .rodata

  parent reply	other threads:[~2022-07-10 20:19 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 [this message]
2022-07-11  1:53 ` jose.marchesi at oracle dot com
2022-08-03 18:21 ` jose.marchesi at oracle dot com
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-XCMOlR2FMO@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: link
Be 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).