From: Satyam Sharma <satyam@infradead.org>
To: Andi Kleen <ak@suse.de>
Cc: Jeff Garzik <jeff@garzik.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>,
len.brown@intel.com, linux-ide@vger.kernel.org, dz@debian.org,
minyard@acm.org, j.w.r.degoede@hhs.nl, lm-sensors@lm-sensors.org,
rlove@rlove.org, bzolnier@gmail.com, dmitry.torokhov@gmail.com,
mzxreary@0pointer.de, stelian@popies.net, ibm-acpi@hmh.eng.br,
ambx1@neo.rr.com, gimli@dark-green.com
Subject: Re: [PATCH] drivers/firmware: const-ify DMI API and internals
Date: Sun, 2 Sep 2007 02:51:53 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.0.999.0709020249190.20781@enigma.security.iitk.ac.in> (raw)
In-Reply-To: <200709011833.08581.ak@suse.de>
On Sat, 1 Sep 2007, Andi Kleen wrote:
>
> > And if we're really lucky, this might enable some additional
> > optimizations on the part of the compiler.
>
> Only if the kernel was compiled C++. C compilers generally ignore constness
> for optimization purposes because it can be so easily casted away.
???
I can't speak for the exact const-ification that Jeff did in this
particular patch, but if you intended your comment up there to be a
blanket statement, then you're totally and horribly wrong. There's a
whole plethora of optimizations that gcc does when dealing with const-
marked data. If you've seen / experienced otherwise, please post some
testcases.
next prev parent reply other threads:[~2007-09-01 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 14:27 Jeff Garzik
2007-09-01 15:36 ` Greg KH
2007-09-01 16:01 ` Jeff Garzik
2007-09-09 17:51 ` Greg KH
2007-09-09 20:24 ` Sam Ravnborg
2007-09-09 21:12 ` Greg KH
2007-09-01 16:33 ` Andi Kleen
2007-09-01 21:21 ` Satyam Sharma [this message]
2007-09-02 17:17 ` [lm-sensors] " Jean Delvare
2007-09-11 21:54 ` Bartlomiej Zolnierkiewicz
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=alpine.LFD.0.999.0709020249190.20781@enigma.security.iitk.ac.in \
--to=satyam@infradead.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ambx1@neo.rr.com \
--cc=bzolnier@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dz@debian.org \
--cc=gimli@dark-green.com \
--cc=greg@kroah.com \
--cc=ibm-acpi@hmh.eng.br \
--cc=j.w.r.degoede@hhs.nl \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=minyard@acm.org \
--cc=mzxreary@0pointer.de \
--cc=rlove@rlove.org \
--cc=stelian@popies.net \
/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
Powered by JetHome