public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Mark Wielaard <mark@klomp.org>
Cc: binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed compile (failure) (master)
Date: Mon, 13 Jun 2022 11:08:20 +0200	[thread overview]
Message-ID: <1e4d5efd-7304-6ff3-5522-f8bf6c90c7cc@suse.com> (raw)
In-Reply-To: <Yqby31VCjuZj4OUa@wildebeest.org>

On 13.06.2022 10:18, Mark Wielaard wrote:
> Looks like this failed on builder that do --enable-target=all with:
> 
> ../../binutils-gdb/opcodes/i386-dis.c: In function ‘print_insn’:
> ../../binutils-gdb/opcodes/i386-dis.c:9827:13: error: invalid type argument of ‘->’ (have ‘instr_info’)
>  9827 |     if (*ins->op_out[i] != '\0')
>       |             ^~

Thanks for pointing this out. I managed to commit an unrefreshed patch.
Should now be fixed.

Jan

  reply	other threads:[~2022-06-13  9:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  8:13 builder
2022-06-13  8:18 ` Mark Wielaard
2022-06-13  9:08   ` Jan Beulich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-09 23:57 builder
2023-01-09 23:46 builder
2022-12-16 12:24 builder
2022-12-12  9:54 builder
2022-12-07  4:25 builder
2022-12-05  0:18 builder
2022-11-30 16:24 builder
2022-11-30 16:21 builder
2022-11-11  6:30 builder
2022-11-01  9:58 builder
2022-10-31 13:36 builder
2022-10-19  9:14 builder
2022-07-08 10:24 builder
2022-06-27 11:11 builder
2022-06-21 10:32 builder
2022-06-21 16:40 ` Mark Wielaard
2022-06-09  0:20 builder
     [not found] ` <CAG_eJLfRrgsK62e7UX_HF7p5O+czBnTm6z+8K=KnDsasadkp5Q@mail.gmail.com>
2022-06-09  3:36   ` Mark Wielaard
2022-06-02 11:05 builder

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=1e4d5efd-7304-6ff3-5522-f8bf6c90c7cc@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=mark@klomp.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).