From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: 970814 and libg++
Date: Sun, 17 Aug 1997 17:17:34 -0000 [thread overview]
Message-ID: <m0x08zw-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: 9708171708.AA03535@modi.xraylith.wisc.edu
>
> btw, static template data members are not being instantiated breaking SGI
> STL in libg++-2.8.0b6 (the allocator in particular). Also, I'm getting a
> core dump when compiling libstdc++ tests when compiling with '-g -O2', but
> with -g. Anybody else seen this? This is on a hppa1.1-hp-hpux10.20 using
> GAS from binutils 2.8.1. I'll investigate this further on other platforms.
>
Same here on Linux/x86.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
WARNING: multiple messages have this Message-ID
From: Andi Kleen <kdp0101@hpmail.lrz-muenchen.de>
To: egcs@cygnus.com
Subject: GCC Projects?
Date: Sun, 17 Aug 1997 17:17:34 -0000 [thread overview]
Message-ID: <m0x08zw-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970817171734.bNVZRgeCssV3oNTfFDABphiBZYh2tRhY5kX7yA9rg6E@z> (raw)
Hi,
I see that there are two main unfinished projects in the egcs
source tree: pre-compiled include files and bytecode generation.
Is anyone working on one of these?
-Andi
next reply other threads:[~1997-08-17 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-17 17:17 H.J. Lu [this message]
1997-08-17 17:17 ` GCC Projects? Andi Kleen
1997-08-17 18:01 970814 and libg++ Mumit Khan
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=m0x08zw-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--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).