linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Changbin Du <changbin.du@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Make perf able to build with latest libbfd
Date: Thu, 30 Jan 2020 11:55:48 +0100	[thread overview]
Message-ID: <20200130105548.GC3841@kernel.org> (raw)
In-Reply-To: <20200129075829.GB1256499@krava>

Em Wed, Jan 29, 2020 at 08:58:29AM +0100, Jiri Olsa escreveu:
> On Tue, Jan 28, 2020 at 11:29:38PM +0800, Changbin Du wrote:
> > libbfd has changed the bfd_section_* macros to inline functions
> > bfd_section_<field> since 2019-09-18. See below two commits:
> >   o http://www.sourceware.org/ml/gdb-cvs/2019-09/msg00064.html
> >   o https://www.sourceware.org/ml/gdb-cvs/2019-09/msg00072.html
> > 
> > This fix make perf able to build with both old and new libbfd.
> > 
> > Signed-off-by: Changbin Du <changbin.du@gmail.com>
> 
> Acked-by: Jiri Olsa <jolsa@redhat.com>

Thanks, applied.

- Arnaldo
 
> thanks,
> jirka
> 
> 
> > ---
> >  tools/perf/util/srcline.c | 16 +++++++++++++++-
> >  1 file changed, 15 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/perf/util/srcline.c b/tools/perf/util/srcline.c
> > index 6ccf6f6d09df..5b7d6c16d33f 100644
> > --- a/tools/perf/util/srcline.c
> > +++ b/tools/perf/util/srcline.c
> > @@ -193,16 +193,30 @@ static void find_address_in_section(bfd *abfd, asection *section, void *data)
> >  	bfd_vma pc, vma;
> >  	bfd_size_type size;
> >  	struct a2l_data *a2l = data;
> > +	flagword flags;
> >  
> >  	if (a2l->found)
> >  		return;
> >  
> > -	if ((bfd_get_section_flags(abfd, section) & SEC_ALLOC) == 0)
> > +#ifdef bfd_get_section_flags
> > +	flags = bfd_get_section_flags(abfd, section);
> > +#else
> > +	flags = bfd_section_flags(section);
> > +#endif
> > +	if ((flags & SEC_ALLOC) == 0)
> >  		return;
> >  
> >  	pc = a2l->addr;
> > +#ifdef bfd_get_section_vma
> >  	vma = bfd_get_section_vma(abfd, section);
> > +#else
> > +	vma = bfd_section_vma(section);
> > +#endif
> > +#ifdef bfd_get_section_size
> >  	size = bfd_get_section_size(section);
> > +#else
> > +	size = bfd_section_size(section);
> > +#endif
> >  
> >  	if (pc < vma || pc >= vma + size)
> >  		return;
> > -- 
> > 2.24.0
> > 
> 

-- 

- Arnaldo

  reply	other threads:[~2020-01-30 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 15:29 [PATCH] perf: Make perf able to build with latest libbfd Changbin Du
2020-01-29  7:58 ` Jiri Olsa
2020-01-30 10:55   ` Arnaldo Carvalho de Melo [this message]
2020-02-16 23:25     ` Stephen Rothwell
2020-05-01  0:17       ` Joel Stanley
2020-02-05 15:45 ` [tip: perf/urgent] " tip-bot2 for Changbin Du
2020-05-31  1:50 ` [PATCH] " Marek Vasut
2020-06-01 16:47   ` Greg KH
     [not found]     ` <46FC68D5-0AB5-45F7-8851-555779C5685F@iscas.ac.cn>
2020-07-16 12:01       ` Greg KH

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=20200130105548.GC3841@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=changbin.du@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@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).