From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Lipe To: Aaron Jackson Cc: egcs@cygnus.com Subject: Re: broken 970929 snapshot Date: Fri, 03 Oct 1997 07:28:00 -0000 Message-id: <19971003092532.41408@dgii.com> References: <9710030628.AA04667@negril.msrce.howard.edu> X-SW-Source: 1997-10/msg00152.html > >Disclaimer: I don't think I've ever seen an Ultrix system in my life. > You might not ever see one in the future since DEC killed them off... :-) > >To prove or disprove this theory, try the following, in decreasing ease: > > Manually compile with file with either -fno-exceptions which > > turns exceptions off completely. > > Compile the file with -fsjlj-exceptions to force the use of > > the setjmp/longjmp exceptions. > > Both flages fixed the problem. OK. This means the code your assembler is finding offensive is related to exceptions - just like the situation I ran into recently. > > Install GNU as. > I'll wait a little before I try this option ;) It really shouldn't be too painful. Ultrix is listed as a supported target in current GAS. > >You can roam through the archives for conversations on this topic. > > I guess I should read more of the posts...but I tend to ignore > subjects that I know nothing about. If we all did that, you'd be a little less close to getting your target to work again, now wouldn't you? :-) > >Experimenting with disabling the DWARF2 exceptions by adding a > > #define DWARF2_UNWIND_INFO 0 > > in your tm.h file > > I'll give it a try. How about on the command line? I'll have > to try that tomrrow afternoon. Sleep now! Don't know of a way to do that. If you specify the flags described above you'll force either no exceptions or non-dwarf2 exceptions. As a kludge, you can change it from '1' to '0' at the end of gcc/defaults.h. > Aaron Jackson jackson@msrce.howard.edu > > > -- Robert Lipe http://www.dgii.com/people/robertl robertl@dgii.com