Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tim Newsome <tim@sifive.com>
To: duane@duaneellis.com
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb <gdb@sourceware.org>
Subject: Re: can target code change architecture setting?
Date: Mon, 10 Oct 2016 19:46:00 -0000	[thread overview]
Message-ID: <CAGDihendk5wTurD+4tesEePK09f3eSxpKZ=0BmDq1dEoaFOiZA@mail.gmail.com> (raw)
In-Reply-To: <20161010094844.5c1bb9f86d671edec44bb378f25c04cc.aef8a9655c.wbe@email03.godaddy.com>

On Mon, Oct 10, 2016 at 9:48 AM,  <duane@duaneellis.com> wrote:

> Question #1 Is this dual mode possible in RISCV?

Not currently, and I don't think there will be a dual mode.

There was a proposal that should allow 32-bit code to just work on
64-bit architectures, but I'm pretty sure it was not by adding a
different mode. It sounded more like the MIPS model where the ISA is
cleverly defined to not care. But unfortunately I can't find the
e-mail thread right now.

> Question #2 - How should the remote debugger respond to GDB?

For RISCV, what I would want is for it to tell GDB that it's running
on 64-bit hardware, because it is. I see no reason to hide from the
user what's actually happening in the hardware.

Tim


  reply	other threads:[~2016-10-10 19:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 16:48 duane
2016-10-10 19:46 ` Tim Newsome [this message]
2016-10-11 11:48 ` Yao Qi
2016-10-11 14:30   ` Duane Ellis
2016-11-03 19:47     ` Doug Evans
  -- strict thread matches above, loose matches on Subject: below --
2016-10-07 17:38 Tim Newsome
2016-10-10  9:26 ` Yao Qi
2016-10-10 15:39   ` Tim Newsome

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='CAGDihendk5wTurD+4tesEePK09f3eSxpKZ=0BmDq1dEoaFOiZA@mail.gmail.com' \
    --to=tim@sifive.com \
    --cc=duane@duaneellis.com \
    --cc=gdb@sourceware.org \
    --cc=qiyaoltc@gmail.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