One of the outstanding issues with the current 20 bit msp430-gcc is
msp430-gdb doesn't understand enough to work properly. msp430-gdb should
also be mutated forward to be based on a more modern gdb. Currently we've
been using 7.2 with the 4.6.3 msp430-gcc toolchain.
Eventually, I hope to take a wack at tweaking gdb to understand the 20 bit
4.7 gcc support. When I do I hope I can get some pointers. More
importantly I will need help figuring out how to feed changes upstream. I
haven't had the pleasure of interacting with upstream GNU/FSF folks so
haven't rented from that particular clue emporium.
Any pointers would be appreciated.
On Wed, Oct 31, 2012 at 10:01 AM, Brendan Conoboy <b...@redhat.com> wrote:
> On 10/31/2012 02:27 AM, David Brown wrote:
> > I fully agree about the benefits of getting msp430 support into the
> > mainline trees for the tools. While there are benefits in having an
> > officially supported (by TI and/or Red Hat) out-of-tree build on the
> > side, everyone wins in having the main work being in-tree. (A typical
> > use of the out-of-tree build would be to apply patches for supporting
> > new devices faster than mainline FSF releases.)
>
> Couldn't have said it better myself. Having the port upstream provides
> a foundation that anybody can build on top of. I hope any such
> additions will ultimately be sent back upstream, but that is up to the
> individual contributor.
>
> > One problem you will face in this move is the copyright situation for
> > many contributions to msp430 gcc, binutils, gdb and libraries.
> [snip]
> > I am
> > sure you will get helpful responses if you can get hold of the
> > appropriate people (and posting to this mailing list is probably a good
> > start), but I fear you will have to do a certain amount of re-writing.
>
> Yes, the copyright situation is quite problematic. Suffice it to say we
> have done and continue to do a significant amount of clean-room coding
> to ensure there will be no copyright issues with upstream submission and
> acceptance.
>
> > However, once you have first completed the merge with upstream, it will
> > make maintenance and development far easier in the future.
>
> Yes!
>
> > I don't know what mailing lists or other channels you will use for
> > communication during this development (I guess the gcc development list
> > at least), but please keep us up to date on this list too.
>
> TI will likely communicate more here wrt the beta Thomas mentioned in
> his initial email, and we'll be watching, discussing there as we go.
> Likewise we'll be active on binutils, gcc, and gdb development lists as
> we have bug reports or patch submissions. The finishing touches, making
> the new msp tools work well for the community, will definitely require a
> lot of discussion, but we're not quite there yet.
>
> > Anyway, good luck in the project - as you say, everyone will win.
>
> Thanks!
>
> --
> Brendan Conoboy / Red Hat, Inc. / b...@redhat.com
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
--
Eric B. Decker
Senior (over 50 :-) Researcher
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
