public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: Jason Merrill <jason@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: init1.C failure under study
Date: Sun, 30 Nov 1997 20:14:00 -0000	[thread overview]
Message-ID: <19971130221357.15784@dgii.com> (raw)
In-Reply-To: <u9ra7yd5a3.fsf@yorick.cygnus.com>

> > This test works on OpenServer ELF, but not COFF.   Whether this is
> > something in the way sco5.h handles initializers, I can't tell.
> 
> > Can anyone offer good hints where to look?
> 
> Does defining HAVE_ATEXIT help?

The problem isn't in the destructors.   The problem seems to be that
the constructors are never called.

RJL

  reply	other threads:[~1997-11-30 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19971129112737.14113.cygnus.egcs@dgii.com>
1997-11-30  3:17 ` Jason Merrill
1997-11-30 20:14   ` Robert Lipe [this message]
1997-11-30 22:31   ` Robert Lipe
1997-11-29  9:29 Robert Lipe

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=19971130221357.15784@dgii.com \
    --to=robertl@dgii.com \
    --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).