public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@cygnus.com
Subject: Re: Strange warning (variable might be clobbered by `longjmp' or`vfork')
Date: Mon, 01 Sep 1997 15:32:00 -0000	[thread overview]
Message-ID: <9709012226.AA26415@moene.indiv.nluug.nl> (raw)
In-Reply-To: <199709011923.PAA16417@jfc.>

Jim Wilson wrote:

> If people think it is important that we have EH support enabled
> by default in the first EGCS release, then someone (me?) will have 
> to spend time looking into this real soon.

And John Carr replied:

>  I consider exception handling important.  I don't know
>  how hard the bugs will be to fix so I can't say whether
>  it is worth delaying the release.

Let me second this.  Joe Buck has made it abundantly clear that the  
one major selling point of the first egcs release is a reliable C++  
compiler reasonably close to the draft standard, with working  
exception handling support.

Although I cannot personally speak for the Fortran community on  
this list, I think that all other goals can be made subordinate to  
that one.  I have the feeling the g77 crowd can wait, especially if  
we (i.e. the g77-dev `inner circle') can produce a g77-0.5.21 to go  
together with gcc-2.7.2.3 that at least solves all the known bugs in  
g77-0.5.20 and then some - which we _can_ *iff* the GNU machines at  
MIT stay on the 'net reliably.

Toon.

  reply	other threads:[~1997-09-01 15:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-31 23:12 Strange warning (variable might be clobbered by `longjmp' or `vfork') Joe Buck
1997-09-01 12:09 ` Jim Wilson
1997-09-01 12:23   ` John Carr
1997-09-01 15:32     ` Toon Moene [this message]
1997-09-02  9:52       ` Strange warning (variable might be clobbered by `longjmp' or Joe Buck
1997-09-02 11:50         ` Jim Wilson
1997-09-02 12:20           ` Joe Buck
1997-09-02 15:24             ` Jim Wilson
1997-09-02 19:15               ` Jeffrey A Law
1997-09-02 19:32                 ` Richard Henderson
1997-09-02 20:05                   ` Jeffrey A Law
1997-09-03 13:09                     ` Richard Henderson
1997-09-01 13:48   ` Wrong debug info on pc-linux-gnu ? Oleg Krivosheev
1997-09-02  6:14     ` Bernd Schmidt
1997-09-03  2:29   ` Strange warning (variable might be clobbered by `longjmp' or `vfork') Andreas Schwab
1997-11-01 21:24 ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1997-08-31 22:48 Jim Wilson
1997-08-31  2:07 egcs 970828 and X11 on linux/x86 H.J. Lu
1997-08-31 18:57 ` Strange warning (variable might be clobbered by `longjmp' or `vfork') Kamil Iskra
1997-08-31  1:23 Jim Wilson
1997-11-01 21:16 ` Jeffrey A Law
1997-08-26 15:53 Mike Stump
1997-08-26 13:14 Tobias Ringstrom

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=9709012226.AA26415@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=egcs@cygnus.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).