public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.edu>
To: egcs@cygnus.com
Subject: Re: Test result for 970814 on native sparc-sun-solaris2.5.1
Date: Tue, 19 Aug 1997 02:36:07 -0000	[thread overview]
Message-ID: <9708190234.AA05546@modi.xraylith.wisc.edu> (raw)
In-Reply-To: m0x0cn4-0004ecC@ocean.lucon.org

hjl@lucon.org (H.J. Lu) writes:
> > 
> >   In message <9708171708.AA03535@modi.xraylith.wisc.edu>you write:
> >   > btw, static template data members are not being instantiated breaking S
> GI
> >   > STL in libg++-2.8.0b6 (the allocator in particular).
> > I assume you're referring to the libstdc++ tests right?  Do you get an
> > error like:
> > 
> > /usr/ccs/bin/ld: Unsatisfied symbols:
> >    __default_alloc_template<false, 0>::end_free(data)
> >    __default_alloc_template<false, 0>::heap_size(data)
> >    __default_alloc_template<false, 0>::free_list(data)
> >    __default_alloc_template<false, 0>::start_free(data)
> > 

Yup. I instantiated these by hand just to test things, but then tmap
core dumped on me with '-g -O2'. The only time tmap works is when I
don't specify '-O*'. 

btw, the instantiations *are* there for i386-linux-gnulibc1, but not
for hppa1.1-hp-hpux10.20. "tmap" dies on either platform with -O*.

Mumit

             reply	other threads:[~1997-08-19  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-19  2:36 Mumit Khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-08-19  1:10 H.J. Lu
1997-08-18  8:13 Klaus Kaempf
1997-08-17 21:55 prototyping H.J. Lu
1997-08-17 22:21 ` Test result for 970814 on native sparc-sun-solaris2.5.1 Alexandre Oliva
1997-08-18  1:03 ` Jeffrey A Law
1997-08-17 17:08 Mumit Khan
1997-08-16 17:50 Mike Stump

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=9708190234.AA05546@modi.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --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).