public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Binutils <binutils@sourceware.org>, gdb@sourceware.org
Subject: Re: [PATCH] RISC-V: Fix gdbserver problem with handling arch strings.
Date: Mon, 27 Jan 2020 20:31:00 -0000	[thread overview]
Message-ID: <CAFyWVab7aKgE1RZypGJf85D21B9wfhZe7Xy1K4MzHKcAS595vQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2001271219510.14118@redsun52.ssa.fujisawa.hgst.com>

On Mon, Jan 27, 2020 at 5:04 AM Maciej W. Rozycki <macro@wdc.com> wrote:
> vs (native):
> p/d check_arg_struct_01_01 (ref_val_struct_01_01)
> $1 = 0
> (gdb) FAIL: gdb.base/infcall-nested-structs.exp: l=c++: types-tf: p/d check_arg_struct_01_01 (ref_val_struct_01_01)
>
> which might be a compiler problem (old `gcc (GCC) 8.2.1 20181105 (Red Hat
> 8.2.1-5)' in the native installation here, vs `riscv64-linux-gnu-gcc (GCC)
> 10.0.0 20191109 (experimental)' in the remote one), which I'll look into
> getting sorted independently, perhaps by wiring a native compiler build
> into my toolchain compilation.

This is
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89627
which was fixed by Andrew Burgess in gcc 9.

Jim

  reply	other threads:[~2020-01-27 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24  2:09 Jim Wilson
2020-01-24 13:32 ` Maciej W. Rozycki
2020-01-24 22:38   ` Jim Wilson
2020-01-27 13:04     ` Maciej W. Rozycki
2020-01-27 20:31       ` Jim Wilson [this message]
2020-01-27 23:24 ` [PATCH v2] " Jim Wilson
2020-01-30 15:41 ` [PATCH] " Palmer Dabbelt via binutils

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=CAFyWVab7aKgE1RZypGJf85D21B9wfhZe7Xy1K4MzHKcAS595vQ@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=macro@wdc.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).