From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] __mcount on ARC
Date: Tue, 20 Feb 2018 15:46:46 +0000 [thread overview]
Message-ID: <1519141605.6393.78.camel@synopsys.com> (raw)
In-Reply-To: <f0f25d75-38f2-8587-61a8-76bf0259247f@gmail.com>
Hi Zoltan,
On Mon, 2018-02-19 at 21:02 +0100, Zoltan Gyarmati wrote:
> Dear All
> On 02/19/2018 09:58 AM, Alexey Brodkin wrote:
> > Hi Zoltan,
> >
> > On Mon, 2018-02-19 at 09:09 +0100, Thomas Petazzoni wrote:
> > > Hello,
[snip]
> Thanks for the background info!
> According to the gprof documentation [1]:
>
> "which causes every function to call mcount (or _mcount, or __mcount, depending on the OS and compiler) as one of its first operations."
>
> And a couldn't find any note about difference between the 3 so it seems we are safe to assume that these are the same.
> Is there any intention to patch the ARC glibc in Buildroot with the mentioned strong_alias (or at later point even the upstream source tree?)
> Any opinions?
>
>
> [1] https://sourceware.org/binutils/docs/gprof/Implementation.html
Keeping in mind your input I really think it worth addressing in glibc for ARC.
And given our port was not yet upstreamed maybe we may squeeze that approach with
an alias as on AArch64 into the next respin of Vineet's patches and we'll
just get new set of patches on top of the most recent glibc in Buildroot.
Or as a short-term solution just to get rid of that build failure right before
Buildroot release we may just hand-copy "strong_alias (__mcount, _mcount);" in
sysdeps/arc/machine-gmon.h.
Which option do you prefer?
-Alexey
next prev parent reply other threads:[~2018-02-20 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 18:45 [Buildroot] __mcount on ARC Zoltan Gyarmati
2018-02-19 8:09 ` Thomas Petazzoni
2018-02-19 8:58 ` Alexey Brodkin
2018-02-19 20:02 ` Zoltan Gyarmati
2018-02-20 15:46 ` Alexey Brodkin [this message]
2018-02-20 20:38 ` Zoltan Gyarmati
2018-02-20 20:53 ` Vineet Gupta
2018-02-21 7:06 ` Alexey Brodkin
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=1519141605.6393.78.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/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