From: Hans-Wolfgang Loidl <hwloidl@informatik.uni-muenchen.de>
To: DJ Delorie <dj@redhat.com>
Cc: gdb@sourceware.org, drow@false.org
Subject: Re: gdb support for m32c?
Date: Fri, 10 Mar 2006 23:12:00 -0000 [thread overview]
Message-ID: <20060311001153.4b5bff3d@anagni.tcs.ifi.lmu.de> (raw)
In-Reply-To: <200603102255.k2AMtTpV006206@greed.delorie.com>
Hi DJ,
On Fri, 10 Mar 2006 17:55:29 -0500
DJ Delorie <dj@redhat.com> wrote:
>
> > In the meantime I managed to build the m32c simulator from the CVS
> > HEAD, and with that version I can now run simple C programs, and
> > also some programs compiled via C from out high-level language So,
> > I'm a happy user (for now)!
>
> Like I said, the patches are minimal. Example: shift counts bigger
> than 16 are not properly truncated, a few more simulated hardware
> bits, etc.
>
> > I noticed, though, that the simulator can't handle argv input: it
> > gives a null pointer reference.
>
> There's no argv support. Boards don't have command lines ;-)
>
> I have a pile of r8c, m16c, and m32c boards on my desk. I try to make
> the simulator compatible with them, so I can run the same images on
> both.
>
> If you're interested in adding argv support, it might be a good idea
> to wait for the gdb integration, since gdb needs to know how to set
> argv also.
It's no biggy; would just be handy for testing stuff. I'll be in touch
if I find more serious things. For now I mainly stick to the simulator,
but in the end we'll work on an m32c based board, to evaluate.
What do you use to flash the code onto the actual board?
Cheers,
--
HW
next prev parent reply other threads:[~2006-03-10 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 21:30 DJ Delorie
2006-03-10 22:45 ` Hans-Wolfgang Loidl
2006-03-10 22:55 ` DJ Delorie
2006-03-10 23:12 ` Hans-Wolfgang Loidl [this message]
2006-03-10 23:21 ` DJ Delorie
2006-03-14 2:23 ` Daniel Jacobowitz
2006-03-14 2:38 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 22:11 Hans-Wolfgang Loidl
2006-03-09 3:24 ` Daniel Jacobowitz
2006-03-09 14:41 ` Hans-Wolfgang Loidl
2006-03-09 15:00 ` Daniel Jacobowitz
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=20060311001153.4b5bff3d@anagni.tcs.ifi.lmu.de \
--to=hwloidl@informatik.uni-muenchen.de \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gdb@sourceware.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