From: Michal Hocko <mhocko@suse.cz>
To: Jason Baron <jbaron@akamai.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [memcg:auto-latest 238/243] include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm'
Date: Mon, 1 Aug 2016 17:29:33 +0200 [thread overview]
Message-ID: <20160801152933.GM13544@dhcp22.suse.cz> (raw)
In-Reply-To: <579F6422.1040202@akamai.com>
On Mon 01-08-16 11:00:50, Jason Baron wrote:
> On 07/31/2016 08:11 AM, Michal Hocko wrote:
> > It seems that this has been already reported and Jason has noticed [1] that
> > the problem is in the disabled optimizations:
> >
> > $ grep CRYPTO_DEV_UX500_DEBUG .config
> > CONFIG_CRYPTO_DEV_UX500_DEBUG=y
> >
> > if I disable this particular option the code compiles just fine. I have
> > no idea what is wrong about the code but it seems to depend on
> > optimizations enabled which sounds a bit scrary...
> >
> > [1] http://www.spinics.net/lists/linux-mm/msg109590.html
>
>
> Hi,
>
> There was a patch from Arnd Bergmann to address this
> issue by removing the usage of -O0 here, included in
> linux-next:
>
> https://marc.info/?l=linux-kernel&m=146701898520633&w=2
AFAIU the code should be fixed as well. See
http://lkml.kernel.org/r/35a0878d-84bd-ad93-8810-23c861ed464e@suse.cz
--
Michal Hocko
SUSE Labs
--
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>
prev parent reply other threads:[~2016-08-01 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 21:04 kbuild test robot
2016-07-31 12:11 ` Michal Hocko
2016-08-01 11:09 ` Michal Hocko
2016-08-01 11:27 ` Martin Liška
2016-08-01 12:41 ` oliver
2016-08-03 5:17 ` Balbir Singh
2016-08-02 15:18 ` Jason Baron
2016-08-01 15:00 ` Jason Baron
2016-08-01 15:29 ` Michal Hocko [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=20160801152933.GM13544@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jbaron@akamai.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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