public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Dodji Seketeli <dodji@seketeli.org>
Cc: libabigail@sourceware.org,
	David Abdurachmanov <david.abdurachmanov@gmail.com>
Subject: Re: Some libabigail RISC-V support issues
Date: Mon, 8 Jan 2024 20:14:36 +0100	[thread overview]
Message-ID: <20240108191436.GA26453@gnu.wildebeest.org> (raw)
In-Reply-To: <87plybvows.fsf@seketeli.org>

Hi Dodji,

On Mon, Jan 08, 2024 at 04:13:39PM +0100, Dodji Seketeli wrote:
> Mark Wielaard <mark@klomp.org> a écrit:
> > [PATCH 1/2] Recognize EM_RISCV in e_machine_to_string
> >
> > Adds support for generating a human readable string for EM_RISCV.
> > It includes configure support in case the system elf.h doesn't
> > contain the macro. But that is just for really old systems, glibc
> > 2.24 added it.
> >
> > Note that elfutils libdw provides dwelf_elf_e_machine_string which
> > does a similar thing.
> 
> Oh, I see that elfutils has it since 0.177.  That's "new" :-).  We
> should then make libabigail's e_machine_to_string use
> dwelf_elf_e_machine_string and require using an elfutils version >= 0.177.  Now
> that elfutils supports pkg-config, it should be easy to require an
> elfutils version.  What do you think?

elfutils 0.177 was released in 2019 so should generally be availble.
It seems a good idea to use dwelf_elf_e_machine_string, but it
produces different descriptions. So it depends on if something depends
on it. If it is just a human readable description then I think the
strings from dwelf_elf_e_machine_string are nicer/more descriptive.

> > [PATCH 2/2] Fix ABG_ASSERT in build_ir_node_from_die for DW_TAG_member
> >
> > Fixes an assert that for some reason only shows up on riscv 
> > in runtesttypesstability against the DWARF for the test file:
> > test-types-stability/PR27165-libzmq.so.5.2.3
> >
> > The issue is that the DIE [2113c8] being checked is in a CU that is 
> > C++, but the dwarf reader current translation unit [b] is a GIMPLE 
> > (lto) one, marked as C99.
> 
> Oh, I see. Good catch.
> >
> > I think this is because that first compile unit contains a variable
> > DIE [35dcf] that has an abstract origin [21492f] with specification
> > [2113c8] and type [211bf6] in the later C++ CU.
> 
> Right.
> 
> > With this make check is all green on riscv.
> 
> Many thanks for this.
> 
> I am applying this patch first, then EM_RISCV one second.  That way, the
> build stays green from the first patch.

And it is green! \o/
https://builder.sourceware.org/buildbot/#/builders/libabigail-ubuntu-riscv

Cheers,

Mark

      reply	other threads:[~2024-01-08 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29  0:40 Mark Wielaard
2023-12-29  0:40 ` [PATCH 1/2] Recognize EM_RISCV in e_machine_to_string Mark Wielaard
2023-12-29  0:40 ` [PATCH 2/2] Fix ABG_ASSERT in build_ir_node_from_die for DW_TAG_member Mark Wielaard
2024-01-08 15:13 ` none Dodji Seketeli
2024-01-08 19:14   ` Mark Wielaard [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=20240108191436.GA26453@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=david.abdurachmanov@gmail.com \
    --cc=dodji@seketeli.org \
    --cc=libabigail@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).