From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Date: Wed, 22 Jun 2016 15:34:54 +0530 [thread overview]
Message-ID: <576A62C6.5080207@synopsys.com> (raw)
In-Reply-To: <20160617144136.GK30927@twins.programming.kicks-ass.net>
On Friday 17 June 2016 08:11 PM, Peter Zijlstra wrote:
> On Fri, Jun 17, 2016@04:39:42PM +0200, Peter Zijlstra wrote:
>> On Fri, Jun 17, 2016@07:36:56AM -0700, Guenter Roeck wrote:
>>> Hi Peter,
>>>
>>> I am seeing build failures in -next when trying to build arc / arcv2 targets.
>>>
>>> arch/arc/include/asm/atomic.h:74:2: error: ?SCOND_FAIL_RETRY_VAR_DEF? undeclared
>>> arch/arc/include/asm/atomic.h:87:2: error: expected ?:? or ?)? before ?SCOND_FAIL_RETRY_ASM?
>>>
>>> Problems seem to be caused by 'locking/atomic, arch/arc: Implement
>>> atomic_fetch_{add,sub,and,andnot,or,xor}()'. Both SCOND_FAIL_RETRY_VAR_DEF and
>>> SCOND_FAIL_RETRY_ASM are undefined.
>>
>> Crud, I messed up the rebase against the backoff reverts. Lemme go do
>> fixups.
>
> I've misplaced my arc compiler, but does this make it go again?
Peter the fixlet below doesn't show up in linux-next yet. Could you please do that
soon. Our internal build lords are yelling at me :-)
To keep things bisectable, it would be desirable to squash this with the orig commit !
>
>
> ---
> arch/arc/include/asm/atomic.h | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h
> index bd9c51cb2bfd..4e3c1b6b0806 100644
> --- a/arch/arc/include/asm/atomic.h
> +++ b/arch/arc/include/asm/atomic.h
> @@ -71,7 +71,6 @@ static inline int atomic_##op##_return(int i, atomic_t *v) \
> static inline int atomic_fetch_##op(int i, atomic_t *v) \
> { \
> unsigned int val, orig; \
> - SCOND_FAIL_RETRY_VAR_DEF \
> \
> /* \
> * Explicit full memory barrier needed before/after as \
> @@ -84,11 +83,8 @@ static inline int atomic_fetch_##op(int i, atomic_t *v) \
> " " #asm_op " %[val], %[orig], %[i] \n" \
> " scond %[val], [%[ctr]] \n" \
> " \n" \
> - SCOND_FAIL_RETRY_ASM \
> - \
> : [val] "=&r" (val), \
> [orig] "=&r" (orig) \
> - SCOND_FAIL_RETRY_VARS \
> : [ctr] "r" (&v->counter), \
> [i] "ir" (i) \
> : "cc"); \
> @@ -199,10 +195,6 @@ ATOMIC_OPS(andnot, &= ~, bic)
> ATOMIC_OPS(or, |=, or)
> ATOMIC_OPS(xor, ^=, xor)
>
> -#undef SCOND_FAIL_RETRY_VAR_DEF
> -#undef SCOND_FAIL_RETRY_ASM
> -#undef SCOND_FAIL_RETRY_VARS
> -
> #else /* CONFIG_ARC_PLAT_EZNPS */
>
> static inline int atomic_read(const atomic_t *v)
>
> _______________________________________________
> linux-snps-arc mailing list
> linux-snps-arc at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-snps-arc
>
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Peter Zijlstra <peterz@infradead.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: <linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Anton Kolesov <Anton.Kolesov@synopsys.com>
Subject: Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Date: Wed, 22 Jun 2016 15:34:54 +0530 [thread overview]
Message-ID: <576A62C6.5080207@synopsys.com> (raw)
In-Reply-To: <20160617144136.GK30927@twins.programming.kicks-ass.net>
On Friday 17 June 2016 08:11 PM, Peter Zijlstra wrote:
> On Fri, Jun 17, 2016 at 04:39:42PM +0200, Peter Zijlstra wrote:
>> On Fri, Jun 17, 2016 at 07:36:56AM -0700, Guenter Roeck wrote:
>>> Hi Peter,
>>>
>>> I am seeing build failures in -next when trying to build arc / arcv2 targets.
>>>
>>> arch/arc/include/asm/atomic.h:74:2: error: ‘SCOND_FAIL_RETRY_VAR_DEF’ undeclared
>>> arch/arc/include/asm/atomic.h:87:2: error: expected ‘:’ or ‘)’ before ‘SCOND_FAIL_RETRY_ASM’
>>>
>>> Problems seem to be caused by 'locking/atomic, arch/arc: Implement
>>> atomic_fetch_{add,sub,and,andnot,or,xor}()'. Both SCOND_FAIL_RETRY_VAR_DEF and
>>> SCOND_FAIL_RETRY_ASM are undefined.
>>
>> Crud, I messed up the rebase against the backoff reverts. Lemme go do
>> fixups.
>
> I've misplaced my arc compiler, but does this make it go again?
Peter the fixlet below doesn't show up in linux-next yet. Could you please do that
soon. Our internal build lords are yelling at me :-)
To keep things bisectable, it would be desirable to squash this with the orig commit !
>
>
> ---
> arch/arc/include/asm/atomic.h | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h
> index bd9c51cb2bfd..4e3c1b6b0806 100644
> --- a/arch/arc/include/asm/atomic.h
> +++ b/arch/arc/include/asm/atomic.h
> @@ -71,7 +71,6 @@ static inline int atomic_##op##_return(int i, atomic_t *v) \
> static inline int atomic_fetch_##op(int i, atomic_t *v) \
> { \
> unsigned int val, orig; \
> - SCOND_FAIL_RETRY_VAR_DEF \
> \
> /* \
> * Explicit full memory barrier needed before/after as \
> @@ -84,11 +83,8 @@ static inline int atomic_fetch_##op(int i, atomic_t *v) \
> " " #asm_op " %[val], %[orig], %[i] \n" \
> " scond %[val], [%[ctr]] \n" \
> " \n" \
> - SCOND_FAIL_RETRY_ASM \
> - \
> : [val] "=&r" (val), \
> [orig] "=&r" (orig) \
> - SCOND_FAIL_RETRY_VARS \
> : [ctr] "r" (&v->counter), \
> [i] "ir" (i) \
> : "cc"); \
> @@ -199,10 +195,6 @@ ATOMIC_OPS(andnot, &= ~, bic)
> ATOMIC_OPS(or, |=, or)
> ATOMIC_OPS(xor, ^=, xor)
>
> -#undef SCOND_FAIL_RETRY_VAR_DEF
> -#undef SCOND_FAIL_RETRY_ASM
> -#undef SCOND_FAIL_RETRY_VARS
> -
> #else /* CONFIG_ARC_PLAT_EZNPS */
>
> static inline int atomic_read(const atomic_t *v)
>
> _______________________________________________
> linux-snps-arc mailing list
> linux-snps-arc@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-snps-arc
>
next prev parent reply other threads:[~2016-06-22 10:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:36 Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Guenter Roeck
2016-06-17 14:36 ` Guenter Roeck
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:41 ` Peter Zijlstra
2016-06-17 14:41 ` Peter Zijlstra
2016-06-17 14:52 ` Guenter Roeck
2016-06-17 14:52 ` Guenter Roeck
2016-06-17 15:00 ` Vineet Gupta
2016-06-17 15:00 ` Vineet Gupta
2016-06-17 15:22 ` Peter Zijlstra
2016-06-17 15:22 ` Peter Zijlstra
2016-06-17 15:36 ` Vineet Gupta
2016-06-17 15:36 ` Vineet Gupta
2016-06-17 16:04 ` Ingo Molnar
2016-06-17 16:04 ` Ingo Molnar
2016-06-17 16:13 ` Peter Zijlstra
2016-06-17 16:13 ` Peter Zijlstra
2016-06-17 20:22 ` Vineet Gupta
2016-06-17 20:22 ` Vineet Gupta
2016-06-17 21:27 ` Guenter Roeck
2016-06-17 21:27 ` Guenter Roeck
2016-06-18 7:05 ` Peter Zijlstra
2016-06-18 7:05 ` Peter Zijlstra
2016-06-18 10:17 ` cross compilers [was build failure of sorts] Peter Zijlstra
2016-06-18 10:17 ` Peter Zijlstra
2016-06-21 5:29 ` Vineet Gupta
2016-06-21 5:29 ` Vineet Gupta
2016-06-21 7:43 ` Peter Zijlstra
2016-06-21 7:43 ` Peter Zijlstra
2016-06-21 9:28 ` Vineet Gupta
2016-06-21 9:28 ` Vineet Gupta
2016-06-21 9:45 ` Peter Zijlstra
2016-06-21 9:45 ` Peter Zijlstra
2016-06-21 9:59 ` Vineet Gupta
2016-06-21 9:59 ` Vineet Gupta
2016-06-21 10:04 ` Peter Zijlstra
2016-06-21 10:04 ` Peter Zijlstra
2016-06-22 10:04 ` Vineet Gupta [this message]
2016-06-22 10:04 ` Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Vineet Gupta
2016-06-22 10:24 ` Peter Zijlstra
2016-06-22 10:24 ` Peter Zijlstra
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=576A62C6.5080207@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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.