All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Quentin Monnet <quentin@isovalent.com>
Cc: open list <linux-kernel@vger.kernel.org>,
	bpf <bpf@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Andrew Burgess <aburgess@redhat.com>
Subject: Re: init_disassemble_info() signature changes causes compile failures
Date: Wed, 22 Jun 2022 16:16:24 -0700	[thread overview]
Message-ID: <20220622231624.t63bkmkzphqvh3kx@alap3.anarazel.de> (raw)
In-Reply-To: <CACdoK4LeRPkACejq87VLFgP-b=y1ZoRX3196f7xEVo-UWm8jWA@mail.gmail.com>

Hi,

On 2022-06-22 23:53:58 +0100, Quentin Monnet wrote:
> Too bad the libbfd API is changing again :/

Yea, not great. Particularly odd that
/* For compatibility with existing code.  */
#define INIT_DISASSEMBLE_INFO(INFO, STREAM, FPRINTF_FUNC, FPRINTF_STYLED_FUNC)  \

was changed. Leaving the "For compatibility with existing code." around,
despite obviously not providing compatibility...

CCed the author of that commit, maybe worth fixing?

Given that disassemble_set_printf() was added, it seems like it'd have been
easy to not change init_disassemble_info() / INIT_DISASSEMBLE_INFO() and
require disassemble_set_printf() to be called to get styled printf support.


> > The fix is easy enough, add a wrapper around fprintf() that conforms to the
> > new signature.
> >
> > However I assume the necessary feature test and wrapper should only be added
> > once? I don't know the kernel stuff well enough to choose the right structure
> > here.
> 
> We can probably find a common header for the wrapper under
> tools/include/. One possibility could be a new header under
> tools/include/tools/, like for libc_compat.h. Although personally I
> don't mind too much about redefining the wrapper several times given
> how short it is, and because maybe some tools could redefine it anyway
> to use colour output in the future.

I'm more bothered by duplicating the necessary ifdefery than duplicating the
short fprintf wrapper...


> The feature test would better be shared, it would probably be similar
> to what was done in the following commit to accommodate for a previous
> change in libbfd:
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fb982666e380c1632a74495b68b3c33a66e76430

Ah, beautiful hand-rolled feature tests :)


> > Attached is my local fix for perf. Obviously would need work to be a real
> > solution.
> 
> Thanks a lot! Would you be willing to submit a patch for the feature
> detection and wrapper?

I'll give it a go, albeit probably not today.

Greetings,

Andres Freund

  reply	other threads:[~2022-06-22 23:16 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 18:19 init_disassemble_info() signature changes causes compile failures Andres Freund
2022-06-22 22:53 ` Quentin Monnet
2022-06-22 23:16   ` Andres Freund [this message]
2022-06-23  9:49     ` Andrew Burgess
2022-07-03  4:48     ` [PATCH v1 0/3] tools: fix compilation failure caused by init_disassemble_info API changes Andres Freund
2022-07-03  4:48       ` [PATCH v1 1/3] tools build: add feature test for " Andres Freund
2022-07-03  4:48       ` [PATCH v1 2/3] tools: add dis-asm-compat.h to centralize handling of version differences Andres Freund
2022-07-03  4:48       ` [PATCH v1 2/3] tools: introduce dis-asm.h wrapper to hide " Andres Freund
2022-07-03  4:54         ` Andres Freund
2022-07-03  4:48       ` [PATCH v1 3/3] tools: Use tools/dis-asm-compat.h to fix compilation errors with new binutils Andres Freund
2022-07-03 21:25     ` [PATCH v2 0/5] tools: fix compilation failure caused by init_disassemble_info API changes Andres Freund
2022-07-03 21:25       ` [PATCH v2 1/5] tools build: add feature test for " Andres Freund
2022-07-03 21:25       ` [PATCH v2 2/5] tools include: add dis-asm-compat.h to handle version differences Andres Freund
2022-07-05 13:44         ` Quentin Monnet
2022-07-15 19:39           ` Andres Freund
2022-07-15 19:46             ` Andres Freund
2022-07-18  8:58             ` Quentin Monnet
2022-07-03 21:25       ` [PATCH v2 3/5] tools perf: Fix compilation error with new binutils Andres Freund
2022-07-03 21:25       ` [PATCH v2 4/5] tools bpf_jit_disasm: " Andres Freund
2022-07-03 21:25       ` [PATCH v2 5/5] tools bpftool: " Andres Freund
2022-07-04  9:13       ` [PATCH v2 0/5] tools: fix compilation failure caused by init_disassemble_info API changes Jiri Olsa
2022-07-04 20:19         ` Andres Freund
2022-07-04 22:12           ` Jiri Olsa
2022-08-01  1:40             ` Andres Freund
2022-07-10 11:43       ` Sedat Dilek
2022-07-10 17:52         ` Sedat Dilek
2022-07-14  9:16       ` Sedat Dilek
2022-07-14 13:25         ` Ben Hutchings
2022-07-15 19:16           ` Andres Freund
2022-07-15 19:18             ` Ben Hutchings
2022-08-01 18:08               ` Arnaldo Carvalho de Melo
2022-07-27 15:47             ` Arnaldo Carvalho de Melo
2022-07-30 21:45               ` Andres Freund
2022-08-01  1:38     ` [PATCH v3 0/8] " Andres Freund
2022-08-01  1:38       ` [PATCH v3 1/8] tools build: Add feature test for " Andres Freund
2022-08-01  1:38       ` [PATCH v3 2/8] tools build: Don't display disassembler-four-args feature test Andres Freund
2022-08-01 18:10         ` Arnaldo Carvalho de Melo
2022-08-01  1:38       ` [PATCH v3 3/8] tools include: add dis-asm-compat.h to handle version differences Andres Freund
2022-08-01 18:05         ` Arnaldo Carvalho de Melo
2022-08-01 18:10           ` Andres Freund
2022-08-01  1:38       ` [PATCH v3 4/8] tools perf: Fix compilation error with new binutils Andres Freund
2022-08-01  1:38       ` [PATCH v3 5/8] tools bpf_jit_disasm: " Andres Freund
2022-08-01  1:38       ` [PATCH v3 6/8] tools bpf_jit_disasm: Don't display disassembler-four-args feature test Andres Freund
2022-08-01 18:27         ` Arnaldo Carvalho de Melo
2022-08-01 18:41           ` Andres Freund
2022-08-01  1:38       ` [PATCH v3 7/8] tools bpftool: Fix compilation error with new binutils Andres Freund
2022-08-01  1:38       ` [PATCH v3 8/8] tools bpftool: Don't display disassembler-four-args feature test Andres Freund
2022-08-01 18:28         ` Arnaldo Carvalho de Melo
2022-08-01 12:45       ` [PATCH v3 0/8] tools: fix compilation failure caused by init_disassemble_info API changes Arnaldo Carvalho de Melo
2022-08-01 15:15         ` Quentin Monnet
2022-08-01 18:02           ` Arnaldo Carvalho de Melo
2022-08-08 13:35             ` Daniel Borkmann
2022-08-01 19:53         ` Jiri Olsa
2022-08-01 19:12       ` Sedat Dilek

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=20220622231624.t63bkmkzphqvh3kx@alap3.anarazel.de \
    --to=andres@anarazel.de \
    --cc=aburgess@redhat.com \
    --cc=acme@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quentin@isovalent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.