Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: Maxim Grigoriev <maxim@tensilica.com>,
	  gdb-patches@sources.redhat.com,
	Bob Wilson <bwilson@tensilica.com>,
	  chris Zankel <zankel@tensilica.com>
Subject: Re: Xtensa port
Date: Fri, 22 Sep 2006 19:11:00 -0000	[thread overview]
Message-ID: <45143542.5060206@hq.tensilica.com> (raw)
In-Reply-To: <1158951165.22863.82.camel@localhost.localdomain>

Michael,

Thanks much for the quick response.
> At a quick first glance, it looks pretty good.
> Do you have a copyright assignment on file
>   
Once in a while, Daniel Jacobowitz mentioned that he has all the 
necessary paper work for Xtensa port. I hope it still true.
> One question -- is there a reason for splitting xtensa-config.c 
> into a separate file?  Not necessarily a problem, but it seems
> to be mostly stuff that would traditionally go in the xxx-tdep.c
> file (such as the struct gdbarch_tdep object).
>   
It's because Xtensa is all about configurability. Historically, 
Tensilica uses a special configuration called FSF for all our FSF 
submissions. It's been used for Xtensa GCC and BFD work. Now, I'm trying 
to use it for GDB. So when we have to deal with a different 
configuration of the Xtensa processor all we need is to update 
xtensa-config.c file.

-- Maxim



  reply	other threads:[~2006-09-22 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 18:25 Maxim Grigoriev
2006-09-22 18:52 ` Michael Snyder
2006-09-22 19:11   ` Maxim Grigoriev [this message]
2006-09-22 20:11     ` Michael Snyder
2006-09-22 21:48       ` Maxim Grigoriev
2006-09-22 23:53         ` Daniel Jacobowitz
2006-09-22 19:07 ` Daniel Jacobowitz
2006-09-22 19:39   ` Maxim Grigoriev
2006-09-22 20:32 ` Jim Blandy
2006-09-22 23:59   ` Maxim Grigoriev

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=45143542.5060206@hq.tensilica.com \
    --to=maxim@tensilica.com \
    --cc=Michael.Snyder@palmsource.com \
    --cc=bwilson@tensilica.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=zankel@tensilica.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