From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-kernel@vger.kernel.org, npiggin@gmail.com,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/uaccess: Use flexible addressing with __put_user()/__get_user()
Date: Tue, 30 Jun 2020 11:33:24 -0500 [thread overview]
Message-ID: <20200630163324.GW3598@gate.crashing.org> (raw)
In-Reply-To: <311c3471-cad7-72d5-a5e6-04cf892c5e41@csgroup.eu>
On Tue, Jun 30, 2020 at 04:55:05PM +0200, Christophe Leroy wrote:
> Le 30/06/2020 à 03:19, Michael Ellerman a écrit :
> >Michael Ellerman <mpe@ellerman.id.au> writes:
> >>Because it uses the "m<>" constraint which didn't work on GCC 4.6.
> >>
> >>https://github.com/linuxppc/issues/issues/297
> >>
> >>So we should be able to pick it up for v5.9 hopefully.
> >
> >It seems to break the build with the kernel.org 4.9.4 compiler and
> >corenet64_smp_defconfig:
>
> Looks like 4.9.4 doesn't accept "m<>" constraint either.
The evidence contradicts this assertion.
> Changing it to "m" make it build.
But that just means something else is wrong.
> >+ make -s CC=powerpc64-linux-gnu-gcc -j 160
> >In file included from /linux/include/linux/uaccess.h:11:0,
> > from /linux/include/linux/sched/task.h:11,
> > from /linux/include/linux/sched/signal.h:9,
> > from /linux/include/linux/rcuwait.h:6,
> > from /linux/include/linux/percpu-rwsem.h:7,
> > from /linux/include/linux/fs.h:33,
> > from /linux/include/linux/huge_mm.h:8,
> > from /linux/include/linux/mm.h:675,
> > from /linux/arch/powerpc/kernel/signal_32.c:17:
> >/linux/arch/powerpc/kernel/signal_32.c: In function
> >'save_user_regs.isra.14.constprop':
> >/linux/arch/powerpc/include/asm/uaccess.h:161:2: error: 'asm' operand has
> >impossible constraints
> > __asm__ __volatile__( \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:197:12: note: in expansion of
> >macro '__put_user_asm'
> > case 4: __put_user_asm(x, ptr, retval, "stw"); break; \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:206:2: note: in expansion of
> >macro '__put_user_size_allowed'
> > __put_user_size_allowed(x, ptr, size, retval); \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:220:2: note: in expansion of
> >macro '__put_user_size'
> > __put_user_size(__pu_val, __pu_addr, __pu_size, __pu_err); \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:96:2: note: in expansion of
> >macro '__put_user_nocheck'
> > __put_user_nocheck((__typeof__(*(ptr)))(x), (ptr), sizeof(*(ptr)))
> > ^
> >/linux/arch/powerpc/kernel/signal_32.c:120:7: note: in expansion of macro
> >'__put_user'
> > if (__put_user((unsigned int)gregs[i], &frame->mc_gregs[i]))
> > ^
Can we see what that was after the macro jungle? Like, the actual
preprocessed code?
Also, what GCC version *does* work on this?
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
npiggin@gmail.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] powerpc/uaccess: Use flexible addressing with __put_user()/__get_user()
Date: Tue, 30 Jun 2020 11:33:24 -0500 [thread overview]
Message-ID: <20200630163324.GW3598@gate.crashing.org> (raw)
In-Reply-To: <311c3471-cad7-72d5-a5e6-04cf892c5e41@csgroup.eu>
On Tue, Jun 30, 2020 at 04:55:05PM +0200, Christophe Leroy wrote:
> Le 30/06/2020 à 03:19, Michael Ellerman a écrit :
> >Michael Ellerman <mpe@ellerman.id.au> writes:
> >>Because it uses the "m<>" constraint which didn't work on GCC 4.6.
> >>
> >>https://github.com/linuxppc/issues/issues/297
> >>
> >>So we should be able to pick it up for v5.9 hopefully.
> >
> >It seems to break the build with the kernel.org 4.9.4 compiler and
> >corenet64_smp_defconfig:
>
> Looks like 4.9.4 doesn't accept "m<>" constraint either.
The evidence contradicts this assertion.
> Changing it to "m" make it build.
But that just means something else is wrong.
> >+ make -s CC=powerpc64-linux-gnu-gcc -j 160
> >In file included from /linux/include/linux/uaccess.h:11:0,
> > from /linux/include/linux/sched/task.h:11,
> > from /linux/include/linux/sched/signal.h:9,
> > from /linux/include/linux/rcuwait.h:6,
> > from /linux/include/linux/percpu-rwsem.h:7,
> > from /linux/include/linux/fs.h:33,
> > from /linux/include/linux/huge_mm.h:8,
> > from /linux/include/linux/mm.h:675,
> > from /linux/arch/powerpc/kernel/signal_32.c:17:
> >/linux/arch/powerpc/kernel/signal_32.c: In function
> >'save_user_regs.isra.14.constprop':
> >/linux/arch/powerpc/include/asm/uaccess.h:161:2: error: 'asm' operand has
> >impossible constraints
> > __asm__ __volatile__( \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:197:12: note: in expansion of
> >macro '__put_user_asm'
> > case 4: __put_user_asm(x, ptr, retval, "stw"); break; \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:206:2: note: in expansion of
> >macro '__put_user_size_allowed'
> > __put_user_size_allowed(x, ptr, size, retval); \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:220:2: note: in expansion of
> >macro '__put_user_size'
> > __put_user_size(__pu_val, __pu_addr, __pu_size, __pu_err); \
> > ^
> >/linux/arch/powerpc/include/asm/uaccess.h:96:2: note: in expansion of
> >macro '__put_user_nocheck'
> > __put_user_nocheck((__typeof__(*(ptr)))(x), (ptr), sizeof(*(ptr)))
> > ^
> >/linux/arch/powerpc/kernel/signal_32.c:120:7: note: in expansion of macro
> >'__put_user'
> > if (__put_user((unsigned int)gregs[i], &frame->mc_gregs[i]))
> > ^
Can we see what that was after the macro jungle? Like, the actual
preprocessed code?
Also, what GCC version *does* work on this?
Segher
next prev parent reply other threads:[~2020-06-30 16:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 12:39 [PATCH v2] powerpc/uaccess: Use flexible addressing with __put_user()/__get_user() Christophe Leroy
2020-04-16 12:39 ` Christophe Leroy
2020-06-29 6:52 ` Christophe Leroy
2020-06-29 11:27 ` Michael Ellerman
2020-06-30 1:19 ` Michael Ellerman
2020-06-30 14:55 ` Christophe Leroy
2020-06-30 16:33 ` Segher Boessenkool [this message]
2020-06-30 16:33 ` Segher Boessenkool
2020-06-30 17:02 ` Christophe Leroy
2020-06-30 17:31 ` Christophe Leroy
2020-06-30 18:53 ` Christophe Leroy
2020-06-30 18:53 ` Christophe Leroy
2020-06-30 21:18 ` Segher Boessenkool
2020-06-30 21:18 ` Segher Boessenkool
2020-07-01 7:05 ` Christophe Leroy
2020-07-01 7:05 ` Christophe Leroy
2020-07-07 12:44 ` Christophe Leroy
2020-07-07 19:02 ` Christophe Leroy
2020-07-08 4:49 ` Christophe Leroy
2020-08-12 12:32 ` Christophe Leroy
2020-08-12 19:30 ` Segher Boessenkool
2020-08-12 19:30 ` Segher Boessenkool
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=20200630163324.GW3598@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.