public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Jason Merrill <jason@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: egcs and exceptions
Date: Tue, 03 Nov 1998 06:36:00 -0000	[thread overview]
Message-ID: <or7lxcsv5m.fsf@araguaia.dcc.unicamp.br> (raw)
In-Reply-To: <u97lxdi8ge.fsf@yorick.cygnus.com>

On Nov  3, 1998, Jason Merrill <jason@cygnus.com> wrote:

>>>>>> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
>> But the doubt is: must you do that, or can you just compile and link
>> foo.cc with -fsjlj-exceptions on Solaris and it will work?

> It may work, but not reliably.

You know...  The more I think about these options that require the
whole library to be rebuilt, the more I believe we should require them 
to be specified at some point in compile-time in order to enable them
at run-time.  Perhaps some additional configure switch that causes
them to be used to build the library and enables the switch by
default, or something that causes multilibs to be created to support
both variants (enabled and disabled) of the particular flag...

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:oliva@gnu.org mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil


  reply	other threads:[~1998-11-03  6:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-22  5:46 Andris Pavenis
1998-10-30  3:25 ` Alexandre Oliva
1998-10-30 14:39   ` Mumit Khan
     [not found] ` <orpvbbt1mq.fsf.cygnus.egcs@araguaia.dcc.unicamp.br>
1998-10-31  2:52   ` Jason Merrill
1998-10-31  5:02     ` Alexandre Oliva
1998-11-02 22:42       ` Jason Merrill
1998-11-03  6:36         ` Alexandre Oliva [this message]
1998-11-04  2:20 Klaus-Georg Adams

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=or7lxcsv5m.fsf@araguaia.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=egcs@cygnus.com \
    --cc=jason@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).