From: Michael Ellerman <mpe@ellerman.id.au>
To: Arnd Bergmann <arnd@arndb.de>, linuxppc-dev@lists.ozlabs.org
Cc: linuxppc-dev@ozlabs.org, linux-mm@kvack.org,
Paul Mackerras <paulus@samba.org>,
aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/mm: Always use STRICT_MM_TYPECHECKS
Date: Thu, 28 Apr 2016 15:27:31 +1000 [thread overview]
Message-ID: <1461821251.25861.4.camel@ellerman.id.au> (raw)
In-Reply-To: <4231376.YDJ7xlGR0L@wuerfel>
On Thu, 2016-04-21 at 11:56 +0200, Arnd Bergmann wrote:
> On Thursday 21 April 2016 13:37:59 Michael Ellerman wrote:
> > Testing done by Paul Mackerras has shown that with a modern compiler
> > there is no negative effect on code generation from enabling
> > STRICT_MM_TYPECHECKS.
> >
> > So remove the option, and always use the strict type definitions.
> >
> > Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> >
>
> I recently ran into the same thing on ARM and have checked the history
> on the symbol. It seems that some architectures cannot pass structures
> in registers as function arguments, but powerpc can, so it was never
> needed in the first place.
Thanks Arnd.
cheers
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-04-28 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 3:37 Michael Ellerman
2016-04-21 4:15 ` Balbir Singh
2016-04-21 6:36 ` Michael Ellerman
2016-04-21 9:56 ` Arnd Bergmann
2016-04-28 5:27 ` Michael Ellerman [this message]
2016-04-28 5:13 ` Paul Mackerras
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=1461821251.25861.4.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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