[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2512092206160.49654@angie.orcam.me.uk>
Date: Tue, 9 Dec 2025 22:25:03 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Alexandre Chartre <alexandre.chartre@...cle.com>
cc: Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>, jpoimboe@...nel.org, peterz@...radead.org,
david.laight.linux@...il.com
Subject: Re: [PATCH v6 03/30] objtool: Disassemble code with libopcodes
instead of running objdump
On Tue, 9 Dec 2025, Alexandre Chartre wrote:
> > Bisect log is attached. I see the problem with gcc 11.4.0, 13.3.0, and
> > 14.3.0. I tried with both Ubuntu 22.04 and 24.04.
>
> This sounds like a configuration issue depending on the binutils version; in
> particular the setting of DISASM_INIT_STYLED (although that's supposed to be
> automatically configured by tools/objtool/Makefile).
I only came across these patches now.
As attractive as it may seem how is this stuff supposed to fly given that
binutils internal libraries promise no stable API to out-of-tree software.
The interfaces can change anytime, just as it is with our internals.
Wouldn't it make sense to improve objdump instead so as to provide the
features required?
Also is it actually legal to link objtool and libopcodes together, given
that they are GPLv2 and GPLv3 respectively?
FWIW asking as one of the binutils contributors and port maintainers.
Maciej
Powered by blists - more mailing lists