This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Ummm, I chose B. What got me to this point is I wrote a very simple program in C that initializes the serial uart and sends the letter T out of the serial port (at least I hoped it would). Then I began investigating my output asm file, my lst file, etc. The deeper I went the more entangled I became in the assembly code and all the directives. Now I am at the point where it looks like I need to learn the Hitachi SH mnemonics and the GNU Assembler just to figure out what is going on with my C program. Earlier someone posted that I should simply write a simple c program, the compiler is smarter than me so let it worry about the assembly language and directives. Well, done that, didn't get anywhere. Alas, I find myself deep in the quagmire of the GNU tools. Oh well, enough whining from me, time to start swimming...in some direction... R.Floyd "Russ.Shaw" wrote: > > GNU compiler tools documentation has always been a problem. > > You can: > A) Get superficial clues from the source code and header files, > B) Practice some simple programs and experiment, > C) Buy a hitachi kit that comes with a free cygnus CD (has lots > more documentation and examples, but not everything), or > D) Buy a support contract (not always affordable, especially > for someone just trying to 'get the hang of it'). > > Robert Floyd wrote: > > > > So I can only conclude that there is no other way for me to begin but to > > get a basic example (my target is going to be a Hitachi SH7032), pick it > > apart, attempt to copy the basics for my own chip but create a very > > simple program such as send characters out the serial port, and see if > > it works. I just find it amazing how anyone ever gets anything done, or > > maybe that is why so many software projects take three times longer than > > management schedules for. ;-) > > > > I am not sure I understand your statement "if you can find a manual for > > one of them, it'll probably be applicable to gas." GNU AS I thought > > must have consistent placement of directives and would not vary > > according to the target since it is an assembler with its own oddities. > > I just don't find all the "rules" for GNU AS laid out clearly anywhere. > > It just appears to be the school of hard knocks all the way. I guess I > > am spoiled by all the commercial assemblers for motorola, intel I have > > bought in the past. > > > > R.Floyd > > > > -- > ******************************************* > * Russell Shaw, B.Eng, M.Eng(Research) * > * email: russell@webaxs.net * > * Victoria, Australia * > ******************************************* ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |