simulavr-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Simulavr-devel] Project Management (was Problem with gdb (not simul


From: Theodore A. Roth
Subject: Re: [Simulavr-devel] Project Management (was Problem with gdb (not simulavr) (disassemble))
Date: Wed, 2 Jan 2002 13:58:51 -0700 (MST)

I haven't had a chance yet to look at what you've changed in gdb in depth.
I'm not saying what you did is wrong. If it is the right fix, there's
nothing else to do.

Are there any other arches in the gdb source based on Harvard? The d10v 
seems to be kinda similar, but not close enough to the avrs.

On another note, anyone have some info on the Harvard arch? I should bone 
up on it a little since all I know about it is that the avr is based on 
it.

Tak, I can add you to the developers of the project, but I'm the only one 
with CVS write access so far. That will change in the future once I feel 
comfortable with a developer. It's still a moot point right now since I am 
still waiting for the savannah guys to contact me about moving my 
repository over.

Ted


On Wed, 2 Jan 2002, Tak Auyeung wrote:

:)I can completely understand Ted's concern about code quality before 
:)integrating it. Maybe we can exploit CVS and use branches to isolate 
:)changes. Then we'll only merge branches to the main trunk after they are 
:)well tested separately. This way, others can contribute to a branch even 
:)when it is not quite ready to be merged to the trunk.
:)
:)As to trying to make changes on to avr-tdep.c, I think changes should
:)be made where they belong. If gdb core code has a bug, fix it in gdb
:)core code. The previously mentioned problem (of using
:)builtin_type_void_data_ptr instead of builtin_type_void_func_ptr) is a
:)bug in the gdb core code and it can affect all pure harvard
:)architecture platforms.
:)
:)Ted, my userid at savannah is tauyeung, I'd be glad to be added to the 
:)developers so I can use a common CVS to track my changes. At the same 
:)time, others can look at the changes easily and help me out when I am 
:)stuck, or make suggestions when I am heading the wrong way. With 
:)branching, my changes should have no impact on the trunk until you 
:)decide the branch is mature enough to be merged.
:)
:)Let me know if I am off base here!
:)
:)--Tak
:)
:)
:)_______________________________________________
:)Simulavr-devel mailing list
:)address@hidden
:)http://mail.freesoftware.fsf.org/mailman/listinfo/simulavr-devel
:)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]