linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: acme@redhat.com (acme@redhat.com)
To: linux-snps-arc@lists.infradead.org
Subject: [RFC] perf: fix building for ARCv1
Date: Fri, 5 Feb 2016 13:10:27 -0300	[thread overview]
Message-ID: <20160205161027.GG28242@kernel.org> (raw)
In-Reply-To: <HE1PR02MB13872D4A7A43E49B8440AEB5D6D20@HE1PR02MB1387.eurprd02.prod.outlook.com>

Em Fri, Feb 05, 2016 at 11:18:52AM +0000, Noam Camus escreveu:
> Well here for EZchip I also see the:
> undefined reference to `__sync_add_and_fetch_4'
> undefined reference to `__sync_sub_and_fetch_4'

Yeah, because there is no: tools/arch/arc/include/asm/atomic.h, can't
you guys adapt arch/arc/include/asm/atomic.h to use in userspace?

- Arnaldo
 
> This is since at file tools/include/asm/atomic.h we use the generic implementation
> If for ARC I could use just like x86 my own header file then functions like:
> atomic_inc()
> atomic_dec_and_test()
> Are easy to implement and you may see an example for such atomic methods in my patch set for the new platform.
> 
> You however wants to use some GCC flag -matomic which I assume somehow will implement the above __sync*.
> I can't find the implementation but if it uses LLSC then it won't work for me since I am not supporting LLSC.

> So seem that either I have my own header at kernel or that I need to
> change the GCC implementation for __sync* to use my atomic
> instructions.  I am personally tend to the x86 solution and not the
> generic one since changing GCC will require to have new compiler
> dependency.

  reply	other threads:[~2016-02-05 16:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1445088959-3058-1-git-send-email-abrodkin@synopsys.com>
2015-10-30  6:21 ` [RFC] perf: fix building for ARCv1 Vineet Gupta
     [not found] ` <C2D7FE5348E1B147BCA15975FBA23075F44C9DD2@IN01WEMBXA.internal.synopsys.com>
     [not found]   ` <1445166916.9672.10.camel@synopsys.com>
     [not found]     ` <87a8rf6a6p.fsf@tassilo.jf.intel.com>
     [not found]       ` <C2D7FE5348E1B147BCA15975FBA23075F44C9E9A@IN01WEMBXA.internal.synopsys.com>
     [not found]         ` <8761235rwe.fsf@tassilo.jf.intel.com>
     [not found]           ` <C2D7FE5348E1B147BCA15975FBA23075F44CAFF9@IN01WEMBXA.internal.synopsys.com>
     [not found]             ` <20151019093549.GK3816@twins.programming.kicks-ass.net>
     [not found]               ` <C2D7FE5348E1B147BCA15975FBA23075F44CB023@IN01WEMBXA.internal.synopsys.com>
     [not found]                 ` <20151019095157.GM3816@twins.programming.kicks-ass.net>
     [not found]                   ` <C2D7FE5348E1B147BCA15975FBA23075F44CB43D@IN01WEMBXA.internal.synopsys.com>
     [not found]                     ` <20151020101133.GA17308@twins.programming.kicks-ass.net>
     [not found]                       ` <C2D7FE5348E1B147BCA15975FBA23075F44CB4BF@IN01WEMBXA.internal.synopsys.com>
2015-10-29 15:58                         ` Alexey Brodkin
2015-10-30  6:19                           ` Vineet Gupta
2016-02-03 16:20                             ` Alexey Brodkin
     [not found]                             ` <1454516455.2811.4.camel__10775.5710989752$1454516490$gmane$org@synopsys.com>
2016-02-04  4:13                               ` Vineet Gupta
2016-02-05 11:18                                 ` Noam Camus
2016-02-05 16:10                                   ` acme [this message]
2016-02-10  3:09                                     ` Vineet Gupta
2016-10-18 18:58               ` Vineet Gupta
2016-10-24 16:17                 ` [PATCH-v2] ARC: syscall for userspace cmpxchg assist Vineet Gupta
2016-11-04 20:16                   ` Vineet Gupta
2016-11-07 18:50                     ` [PATCH] ARC: tweak semantics of " Vineet Gupta

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=20160205161027.GG28242@kernel.org \
    --to=acme@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).