From: Jamie Lokier <jamie@shareable.org>
To: Daniel Egger <degger@fhm.edu>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
herbert@13thfloor.at,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: UP optimizations ..
Date: Fri, 29 Aug 2003 07:53:32 +0100 [thread overview]
Message-ID: <20030829065332.GA12978@mail.jlokier.co.uk> (raw)
In-Reply-To: <1062058995.965.2.camel@sonja>
Daniel Egger wrote:
> Shouldn't these be marked const?
1. There's no need, because they are inline and simple enough to optimise.
2. GCC seems to ignore const and pure attributes on inline functions,
even when that would enable optimisation that it cannot see from the
function body.
-- Jamie
prev parent reply other threads:[~2003-08-29 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 16:03 Herbert Pötzl
2003-08-27 18:17 ` Mikael Pettersson
2003-08-27 18:34 ` Herbert Pötzl
2003-08-28 8:23 ` Daniel Egger
2003-08-29 6:53 ` Jamie Lokier [this message]
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=20030829065332.GA12978@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=degger@fhm.edu \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®