public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: STL[quick questions]
@ 1998-12-07 14:02 Mike Stump
  1998-12-07 14:36 ` Joe Buck
  0 siblings, 1 reply; 6+ messages in thread
From: Mike Stump @ 1998-12-07 14:02 UTC (permalink / raw)
  To: jbuck; +Cc: egcs

> From: Joe Buck <jbuck@Synopsys.COM>
> To: imarkov@math.ucla.edu (Igor Markov)
> Date: Fri, 4 Dec 98 18:47:36 PST

> The reason for not switching for 1.1 was bad timing, and 1.1.1 was
> supposed to be binary compatible so we didn't switch.

I suspect that we'll break binary compatibility with the newer STL.
If we do, then turning on all the abi breaking stuff for 1.2 would be
good, if the new code is ready in time.

Or are people more interested in maintaining what binary compatibility
we can between 1.1.1 and 1.2 (even if it isn' t complete
compatibility)?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: STL[quick questions]
  1998-12-07 14:02 STL[quick questions] Mike Stump
@ 1998-12-07 14:36 ` Joe Buck
  0 siblings, 0 replies; 6+ messages in thread
From: Joe Buck @ 1998-12-07 14:36 UTC (permalink / raw)
  To: Mike Stump; +Cc: jbuck, egcs

> > From: Joe Buck <jbuck@Synopsys.COM>
> > To: imarkov@math.ucla.edu (Igor Markov)
> > Date: Fri, 4 Dec 98 18:47:36 PST
> 
> > The reason for not switching for 1.1 was bad timing, and 1.1.1 was
> > supposed to be binary compatible so we didn't switch.
> 
> I suspect that we'll break binary compatibility with the newer STL.
> If we do, then turning on all the abi breaking stuff for 1.2 would be
> good, if the new code is ready in time.

We still don't have a C++ library that lives in std (the libstdc++ version
3 is not ready).  However, it would be possible to turn on -fsquangle and
the new class layout (that uses 0 bytes for empty classes in almost all
cases).

> Or are people more interested in maintaining what binary compatibility
> we can between 1.1.1 and 1.2 (even if it isn' t complete
> compatibility)?

I don't know.  In practice, the new STL won't break most binary interfaces
because relatively functions depend on STL, and even for those that do,
many of the STL classes have not changed layout.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: STL[quick questions]
  1998-12-04 14:23 Igor Markov
  1998-12-04 18:48 ` Joe Buck
@ 1998-12-30 11:18 ` Gerald Pfeifer
  1 sibling, 0 replies; 6+ messages in thread
From: Gerald Pfeifer @ 1998-12-30 11:18 UTC (permalink / raw)
  To: Igor Markov; +Cc: egcs

On Fri, 4 Dec 1998, Igor Markov wrote:
> A couple of quick questions that I couldn't answer by reading egcs FAQ
> (it looks very sketchy in general -- no top-down structure etc)

This FAQ is maintained by volunteers. If you have any concrete suggestions
resp. patches I'll be happy to discuss these with you resp. install it.

Actually I have been working to improve the FAQ since I assumed web page
maintainership and I'm planing a complete restructuring, but again: The
best way to improve things is by contributing yourself (as a couple of
others have done recently).

> The link to egcs-testrsults archives points nowhere

Which link? On which page have you spotted that?

Provided sufficient information, I'll immediately fix that.

Gerald
-- 
Gerald Pfeifer (Jerry)      Vienna University of Technology
pfeifer@dbai.tuwien.ac.at   http://www.dbai.tuwien.ac.at/~pfeifer/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: STL[quick questions]
  1998-12-04 18:48 ` Joe Buck
@ 1998-12-04 19:02   ` Gerald Pfeifer
  0 siblings, 0 replies; 6+ messages in thread
From: Gerald Pfeifer @ 1998-12-04 19:02 UTC (permalink / raw)
  To: Igor Markov; +Cc: Joe Buck, egcs

On Fri, 4 Dec 1998, Joe Buck wrote:
>> I was wondering if egcs distributoins are going to
>> have the latest available SGI STL? This would be very
>> convenient assuming testing will be done in advance.
> Last time we discussed this, we said we'd switch STL versions for 1.2.

The mainline (and thus all recent snapshots) have been using SGI STL
3.11 for three months now without major problems, as far as I can tell.

1998-09-02  Jason Merrill  <jason@yorick.cygnus.com>

        * algorithm alloc.h defalloc.h hash_map.h hash_set.h iterator
        memory pthread_alloc pthread_alloc.h rope ropeimpl.h stl_algo.h
        stl_algobase.h stl_alloc.h stl_bvector.h stl_config.h
        stl_construct.h stl_deque.h stl_function.h stl_hash_fun.h
        stl_hash_map.h stl_hash_set.h stl_hashtable.h stl_heap.h
        stl_iterator.h stl_list.h stl_map.h stl_multimap.h stl_multiset.h
        stl_numeric.h stl_pair.h stl_queue.h stl_raw_storage_iter.h
        stl_relops.h stl_rope.h stl_set.h stl_slist.h stl_stack.h
        stl_tempbuf.h stl_tree.h stl_uninitialized.h stl_vector.h
        tempbuf.h type_traits.h: Update to SGI STL 3.11.

>> I see many posts about STL on the egcs list, but no
>> clear indication if, say, SGI STL 3.11 works with egcs-1.1.1
>> on Solaris2.6, Linux2 or Windows NT4.0
> As far as I know, it works, but you need to make sure you don't
> wind up mixing headers from the two versions.

Igor, if your really want to/have to use STL 3.11, using a current
snapshot should be reasonably stable on sparc-sun-solaris2.6 (I'm
using that for everyday work) and most probably also on Linux.

Gerald
-- 
Gerald Pfeifer (Jerry)      Vienna University of Technology
pfeifer@dbai.tuwien.ac.at   http://www.dbai.tuwien.ac.at/~pfeifer/

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: STL[quick questions]
  1998-12-04 14:23 Igor Markov
@ 1998-12-04 18:48 ` Joe Buck
  1998-12-04 19:02   ` Gerald Pfeifer
  1998-12-30 11:18 ` Gerald Pfeifer
  1 sibling, 1 reply; 6+ messages in thread
From: Joe Buck @ 1998-12-04 18:48 UTC (permalink / raw)
  To: Igor Markov; +Cc: egcs

>     I was wondering if egcs distributoins are going to
>   have the latest available SGI STL? This would be very
>   convenient assuming testing will be done in advance.

Last time we discussed this, we said we'd switch STL versions for 1.2.

>     I see many posts about STL on the egcs list, but no
>   clear indication if, say, SGI STL 3.11 works with egcs-1.1.1
>   on Solaris2.6, Linux2 or Windows NT4.0

As far as I know, it works, but you need to make sure you don't
wind up mixing headers from the two versions.  The reason for not
switching for 1.1 was bad timing, and 1.1.1 was supposed to be
binary compatible so we didn't switch.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* STL[quick questions]
@ 1998-12-04 14:23 Igor Markov
  1998-12-04 18:48 ` Joe Buck
  1998-12-30 11:18 ` Gerald Pfeifer
  0 siblings, 2 replies; 6+ messages in thread
From: Igor Markov @ 1998-12-04 14:23 UTC (permalink / raw)
  To: egcs

  Hello,

    A couple of quick questions that I couldn't answer by
  reading egcs FAQ (it looks very sketchy in general -- no
  top-down structure etc)

    I was wondering if egcs distributoins are going to
  have the latest available SGI STL? This would be very
  convenient assuming testing will be done in advance.

    I see many posts about STL on the egcs list, but no
  clear indication if, say, SGI STL 3.11 works with egcs-1.1.1
  on Solaris2.6, Linux2 or Windows NT4.0

    The link to egcs-testrsults archives points nowhere,
  but even if this is fixed, I'd prefer a simple compatibility
  table accessible from  http://egcs.cygnus.com

 thanks,    
  
-- 
								Igor
  P.S. Please cc: imarkov@ucla.edu
--------------------------------------------------------------------
What should you do if you see an endangered animal eating an 
endangered plant?

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~1998-12-30 11:18 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-12-07 14:02 STL[quick questions] Mike Stump
1998-12-07 14:36 ` Joe Buck
  -- strict thread matches above, loose matches on Subject: below --
1998-12-04 14:23 Igor Markov
1998-12-04 18:48 ` Joe Buck
1998-12-04 19:02   ` Gerald Pfeifer
1998-12-30 11:18 ` Gerald Pfeifer

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).