Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, nickc@redhat.com
Subject: Re: [PATCH 2/3] sim: msp430: set initial PC to ELF entry if available
Date: Mon, 10 Mar 2014 21:09:00 -0000	[thread overview]
Message-ID: <201403102109.s2AL9PZB015528@greed.delorie.com> (raw)
In-Reply-To: <1394256493-15084-2-git-send-email-vapier@gentoo.org> (message	from Mike Frysinger on Sat, 8 Mar 2014 00:28:12 -0500)


In the case where there *is* a valid reset vector, I think it would be
much better to honor it than to choose some other "arbitrary" (in
terms of hardware simulation) entry point.

Just because the other simulators don't accurately simulate the
hardware, doesn't mean they all shouldn't.

Also, the libgloss for msp430 always sets a valid reset vector, so all
the "simple ELFs" you create should already work.


  parent reply	other threads:[~2014-03-10 21:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08  5:28 [PATCH 1/3] sim: msp430: fix build time warnings Mike Frysinger
2014-03-08  5:28 ` [PATCH 2/3] sim: msp430: set initial PC to ELF entry if available Mike Frysinger
2014-03-10 13:19   ` Nicholas Clifton
2014-03-10 21:09   ` DJ Delorie [this message]
2014-03-10 22:28     ` Mike Frysinger
2014-03-11  3:38   ` [PATCH v2] " Mike Frysinger
2014-03-11  3:44     ` DJ Delorie
2014-03-11  3:57       ` Mike Frysinger
2014-03-11  4:12         ` DJ Delorie
2014-03-08  5:28 ` [PATCH 3/3] sim: msp430: start a test framework Mike Frysinger
2014-03-10 13:56   ` Nicholas Clifton
2014-03-10 13:18 ` [PATCH 1/3] sim: msp430: fix build time warnings Nicholas Clifton
2014-03-10 19:30   ` Mike Frysinger
2014-03-11 16:08     ` Nicholas Clifton
2014-03-11 19:01       ` Mike Frysinger

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=201403102109.s2AL9PZB015528@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=vapier@gentoo.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