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] |
Hi! I've scanned info gcc and ml/crossgcc, but I want to make sure I haven't exhausted all options... I'm using the Hitachi SH-2 for a project, and I know that gcc's calling convention places some arguments in registers, and others on the stack. What I need, however, is some way to force gcc to pass all arguments on the stack, so that I can look through a stack dump and see what was passed to whom. One solution, I suppose, is to disable the registers that gcc passes arguments in. But I want gcc to use these registers, just not for parameter passing. Is there a way to get gcc to do this? I'm willing to hack on the compiler a bit, if someone will help lead me through it--- I currently have no experience with gcc internals. Other approaches to this "core dump"-type debugging approach are also welcome. Thanks! b.g. -- Bill Gatliff bgat@open-widgets.com ------ 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] |