public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: Alan Modra <amodra@gmail.com>,
	"Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: binutils@sourceware.org, Nick Alcock <nick.alcock@oracle.com>
Subject: Re: [PATCH, V5 00/10] Definition and Implementation of CTF Frame format
Date: Thu, 28 Jul 2022 09:19:26 -0700	[thread overview]
Message-ID: <1c3436a1-05ba-9bb1-5acc-df83bd0f9919@oracle.com> (raw)
In-Reply-To: <YuHtfy5JqhmfXZ43@squeak.grove.modra.org>

On 7/27/22 6:59 PM, Alan Modra wrote:
> On Wed, Jul 20, 2022 at 06:19:23PM +0200, Jose E. Marchesi via Binutils wrote:
>> Any chance we can have a review for this patch series?
> 
> I applied the patch series, regenerated libctfframe/configure, and ran
> my normal set of regression tests.  The libctfframe tests failed on
> every target.  On native x86_64-linux:
> 
> libctfframe/testsuite/libctfframe.decode/bigendian_data.c:91:24: warning: too many arguments for format
> [-Wformat-extra-args]
>     91 |       fprintf (stderr, "Decode: Fail to get funcdesc\n", ctf_frame_errmsg (err));
>        |                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> On any cross-target I get ERROR: $target-cc does not exist, or
> complaints like ./.libs/libctfframe.a(libctfframe_la-ctf-frame.o):
> Relocations in generic ELF (EM: 62).  That's due to trying to link
> host objects into a target executable.
> 

I will look into these cross-target failures etc and post V6 with fixes.

Thanks for trying the patch series out and reporting these. My testing 
workflow was carelessly missing libctfframe folder for regression 
testing for cross-builds.

Indu

> So, no, the patch series is not OK without that fixed.  I did glance
> over the patches and other than that they look OK, but I would expect
> Nick Alcock to handle most of the review.
> 


      parent reply	other threads:[~2022-07-28 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17  8:20 [PATCH,V5 " Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 01/10] ctf-frame.h: Add CTF Frame format definition Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 02/10] gas: add new command line option --gctf-frame Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 03/10] gas: generate .ctf_frame Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 04/10] libctfframe: add the CTF Frame library Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 05/10] libctfframe: add GNU poke pickles for CTF Frame Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 06/10] bfd: linker: merge .ctf_frame sections Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 07/10] readelf/objdump: support for CTF Frame section Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 08/10] unwinder: generate backtrace using CTF Frame format Indu Bhagat
2022-07-17  8:20 ` [PATCH,V5 09/10] unwinder: Add CTF Frame unwinder tests Indu Bhagat
2022-07-17  8:20 ` [PATCH, V5 10/10] gdb: sim: buildsystem changes to accommodate libctfframe Indu Bhagat
2022-07-20 16:19 ` [PATCH, V5 00/10] Definition and Implementation of CTF Frame format Jose E. Marchesi
2022-07-28  1:59   ` Alan Modra
2022-07-28 14:37     ` Nick Alcock
2022-07-28 16:19     ` Indu Bhagat [this message]

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=1c3436a1-05ba-9bb1-5acc-df83bd0f9919@oracle.com \
    --to=indu.bhagat@oracle.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=nick.alcock@oracle.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).