Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'

Subject: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
From: peterz@xxxxxxxxxxxxx (Peter Zijlstra)
Date: Fri, 17 Jun 2016 17:22:08 +0200
In-reply-to: <576410AB.6050204@synopsys.com>
References: <57640B08.4090007@roeck-us.net> <20160617143942.GV30154@twins.programming.kicks-ass.net> <20160617144136.GK30927@twins.programming.kicks-ass.net> <57640EB5.8090604@roeck-us.net> <576410AB.6050204@synopsys.com>


Question; why does atomic_read() have a full memory clobber on arc?

Will thinks its because you don't use a memory constraint for *v.

Follow-Ups:
- Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
  - From: Vineet Gupta

References:
- Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
  - From: Guenter Roeck
- Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
  - From: Peter Zijlstra
- Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
  - From: Peter Zijlstra
- Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
  - From: Guenter Roeck
- Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
  - From: Vineet Gupta