From: David Brown <david.brown@hesbynett.no>
To: Andrea Corallo <andrea.corallo@arm.com>
Cc: gcc-help@gcc.gnu.org, stefan@franke.ms,
Stefan Franke <s.franke@bebbosoft.de>
Subject: Re: AW: Correct way to express to the compiler "this does not get clobbered"?
Date: Sat, 5 Dec 2020 20:07:16 +0100 [thread overview]
Message-ID: <dc100e75-ebac-b913-80d4-c62665530721@hesbynett.no> (raw)
In-Reply-To: <gkr1rg4xiti.fsf@arm.com>
On 05/12/2020 18:29, Andrea Corallo via Gcc-help wrote:
> David Brown <david.brown@hesbynett.no> writes:
>
> [...]
>
>> There is no way in C to say that there can't be anything else that
>> changes the object.
>
> I think it would be nice to have, if not in C at least in GCC.
>
> Andrea
>
Agreed. But I think there are so many possible things about constness
that it would be nice to have, that it could quickly get out of hand.
I'd really like a way to tell the compiler that a given object gets set
once during some early function in the program, and can never change
after that. But I can't think of any good syntax for that.
next prev parent reply other threads:[~2020-12-05 19:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 11:47 Andrea Corallo
2020-12-03 12:04 ` Richard Earnshaw
2020-12-03 12:28 ` Andrea Corallo
2020-12-03 13:06 ` Richard Earnshaw
2020-12-03 13:40 ` Andrea Corallo
2020-12-03 18:24 ` David Brown
2020-12-03 23:00 ` Andrea Corallo
2020-12-04 7:23 ` stefan
2020-12-04 9:52 ` Andrea Corallo
2020-12-04 17:27 ` Segher Boessenkool
2020-12-04 18:16 ` Andrea Corallo
2020-12-04 18:33 ` Segher Boessenkool
2020-12-04 18:45 ` Andrea Corallo
[not found] ` <017701d6ca6d$7dc8dc90$795a95b0$@bebbosoft.de>
2020-12-04 18:57 ` AW: " Stefan Franke
2020-12-04 22:52 ` Andrea Corallo
2020-12-05 14:01 ` David Brown
2020-12-05 14:17 ` AW: " Stefan Franke
2020-12-05 18:10 ` Andrea Corallo
2020-12-07 22:27 ` Segher Boessenkool
2020-12-05 19:03 ` David Brown
2020-12-06 11:29 ` AW: " Stefan Franke
2020-12-05 17:29 ` Andrea Corallo
2020-12-05 19:07 ` David Brown [this message]
2020-12-06 9:22 ` Jonathan Wakely
2020-12-04 8:27 ` David Brown
2020-12-04 10:05 ` Andrea Corallo
2020-12-05 8:06 ` Liu Hao
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=dc100e75-ebac-b913-80d4-c62665530721@hesbynett.no \
--to=david.brown@hesbynett.no \
--cc=andrea.corallo@arm.com \
--cc=gcc-help@gcc.gnu.org \
--cc=s.franke@bebbosoft.de \
--cc=stefan@franke.ms \
/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).