Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!boulder.colorado.edu!grunwald From: grunwald@foobar.colorado.edu (Dirk Grunwald) Newsgroups: comp.lang.c++ Subject: Re: implementation/mips/dec/ultrix Message-ID: Date: 21 Sep 89 01:09:26 GMT References: <2348@hub.UUCP> <3838@itivax.iti.org> Sender: news@boulder.Colorado.EDU Reply-To: grunwald@foobar.colorado.edu Followup-To: comp.lang.c++ Organization: University of Colorado, Boulder Lines: 22 In-reply-to: scs@itivax.iti.org's message of 20 Sep 89 16:30:43 GMT This is not completely true. You can use gcc and g++ on the MIPS box. You can generate line-location information for the MIPS box. What you can't do is provide SDB/DBX information directly. The current MIPS assembler does not have a debugging (SDB/DBX) interface. From correspondence with various people, MIPS plans on adding this feature, but we'd be ill advised to hold our collective breath. Alternate solutions require producing the magic .T file, to be consumed by the as1 pass. This, while difficult, is not insurmountable. The other alternate, having GAS mimic the function of the MIPS assembler, seems more difficult. The MIPS assembler is fairly sophisticated. I'm looking at the complexity of generating the .T file - I don't know how hard this is yet, but I do have A Guiding Example. If someone else is burning to do this, please go right ahead - mail me and I'll see if I can't disseminate my information to you. Dirk Grunwald -- Univ. of Colorado at Boulder (grunwald@foobar.colorado.edu)