Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: DJ Delorie <dj@redhat.com>
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 22:28:00 -0000	[thread overview]
Message-ID: <10346094.t4n5KZ1GG2@vapier> (raw)
In-Reply-To: <201403102109.s2AL9PZB015528@greed.delorie.com>

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

On Mon 10 Mar 2014 17:09:25 DJ Delorie wrote:
> 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.

i'm fine with making the default virtual environment fallback to the entry 
point when the reset vector is 0.

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

we're talking about the virtual environment here, not the operating 
environment.  seems a bit funny belittling other ports when the msp430 sim 
itself doesn't properly support simulating the hardware ;).  the few random 
hacks it has in place to try and emulate a few choice aspects of the hardware 
doesn't mean it accurately simulates things either.

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

newlib/libgloss requires a compiler which isn't appropriate from most sim 
tests.  using C for higher level things is perfectly reasonable (especially 
when validating hardware peripheral simulation), but there should be pure 
assembly tests that focus on the ISA.

it's also how i tend to personally test things when it comes to the sim & low 
level hardware -- i use gas+ld only.  a C runtime is a luxury and just gets in 
the way :).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-03-10 22:28 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 3/3] sim: msp430: start a test framework Mike Frysinger
2014-03-10 13:56   ` Nicholas Clifton
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
2014-03-10 22:28     ` Mike Frysinger [this message]
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-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=10346094.t4n5KZ1GG2@vapier \
    --to=vapier@gentoo.org \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.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