From: Paolo Carlini <pcarlini@unitus.it>
To: gp.bolton@computer.org
Cc: gcc <gcc@gnu.org>
Subject: Const warning? (was: Re: [Patch] More redundant...)
Date: Mon, 21 Apr 2003 02:21:00 -0000 [thread overview]
Message-ID: <3EA2EAB5.3040101@unitus.it> (raw)
In-Reply-To: <3EA1B709.3060204@free.fr>
[discussion moved to gcc]
Gawain Bolton wrote:
> These patches to add "const" make me wonder if the compiler couldn't
> help us.
>
> I thinking about a warning for variables which the compiler can see
> are not modified. Something like:
>
> Warning: Variable x should be const.
>
> Is this possible? Could this be useful?
Hi Gawain (by the way those patches mainly remove some NULL pointer
checks, only secondarily const-ify variables).
I find your question interesting: as for many other warnings of this
kind (unreachable code, uninitialized variables, and so on) how many
such warnings would be missed or spuriously emitted would constitute a
good testbed for the optimizers of the compiler. Ideally the code
generated would be identical with and without const qualifiers but we
all know that in the real world this is not the case!
Ideas from the compiler people???
Paolo.
next parent reply other threads:[~2003-04-20 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EA18026.70900@unitus.it>
[not found] ` <3EA1B709.3060204@free.fr>
2003-04-21 2:21 ` Paolo Carlini [this message]
2003-04-21 4:58 ` Kaveh R. Ghazi
2003-04-21 16:06 ` Gawain Bolton
2003-04-22 0:07 Robert Dewar
2003-04-22 6:52 John Reiser
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=3EA2EAB5.3040101@unitus.it \
--to=pcarlini@unitus.it \
--cc=gcc@gnu.org \
--cc=gp.bolton@computer.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).