public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aaron Jackson <jackson@negril.msrce.howard.edu>
To: jackson@negril.msrce.howard.edu, robertl@dgii.com
Cc: egcs@cygnus.com
Subject: Re: broken 970929 snapshot
Date: Thu, 02 Oct 1997 23:35:00 -0000	[thread overview]
Message-ID: <9710030628.AA04667@negril.msrce.howard.edu> (raw)

>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.

>        Install GNU as.

I'll wait a little before I try this option ;)

>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.

>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!

Aaron Jackson		jackson@msrce.howard.edu


             reply	other threads:[~1997-10-02 23:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-02 23:35 Aaron Jackson [this message]
1997-10-03  7:28 ` Robert Lipe
  -- strict thread matches above, loose matches on Subject: below --
1997-10-03 13:24 jackson
1997-10-02 21:56 Aaron Jackson
1997-10-02 23:01 ` Robert Lipe
1997-10-02 16:51 Aaron Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9710030628.AA04667@negril.msrce.howard.edu \
    --to=jackson@negril.msrce.howard.edu \
    --cc=egcs@cygnus.com \
    --cc=robertl@dgii.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).