From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: [PATCH] const mips_io_port_base !?
Date: Tue, 27 Nov 2001 17:15:44 +1100 [thread overview]
Message-ID: <20011127171544.A29424@dea.linux-mips.net> (raw)
In-Reply-To: <20011127010214.B21296@paradigm.rfc822.org>; from flo@rfc822.org on Tue, Nov 27, 2001 at 01:02:14AM +0100
On Tue, Nov 27, 2001 at 01:02:14AM +0100, Florian Lohoff wrote:
Blame whoever designed C that there is no sane way to give a variable an
attribute like "will never change again after the first initalization thus
keeping the value in a register beyond function calls and any other kind
of memory barrier is ok". This inconsistence merily achieves a better
optimization of the code; the set_* function is intended to hide this cute
little standard violation away ...
Ralf
next prev parent reply other threads:[~2001-11-27 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 0:02 [PATCH] const mips_io_port_base !? Florian Lohoff
2001-11-27 6:15 ` Ralf Baechle [this message]
2001-11-28 13:13 ` Florian Lohoff
2001-11-28 17:16 ` H . J . Lu
2001-11-28 17:23 ` James Simmons
2001-11-29 3:55 ` Ralf Baechle
2001-11-29 4:14 ` Paul Mundt
2001-11-29 14:18 ` Ralf Baechle
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=20011127171544.A29424@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
/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