[Bug libstdc++/33832] New: Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[Bug libstdc++/33832] New: Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[hjl at lucon dot org]

Revision 129442

http://gcc.gnu.org/ml/gcc-cvs/2007-10/msg00547.html

moved a few header files from include/ext to include/backward, which
introduced a new libstdc++ API. If a C++ applications want to support
both 4.2 and 4.3 APIs, it needs a way to tell different APIs, something
like


#if GLIBCXX_API == 43
#include <ext/hash_set>
#else
#include <backward/hash_set>
#endif


-- 
           Summary: Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++
                    API
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl at lucon dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[hjl at lucon dot org]

------- Comment #1 from hjl at lucon dot org  2007-10-21 21:45 -------
I believe we should add those deleted ext/xxx header files with

#warning __FILE__ is deprecated ....
#include <backward/xxx>

if we want to move ext/xxx to backward/xxx. It is never a good idea to break
the existing C++ applications for no very good reasons.


-- 

hjl at lucon dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |blocker


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[bkoz at gcc dot gnu dot org]

-- 

bkoz at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |bkoz at gcc dot gnu dot org
                   |dot org                     |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-10-31 21:35:26
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[pinskia at gcc dot gnu dot org]

------- Comment #2 from pinskia at gcc dot gnu dot org  2007-12-08 23:24 -------
Any news on this issue?


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu dot
                   |                            |org
   Target Milestone|---                         |4.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[olafvdspek at gmail dot com]

------- Comment #3 from olafvdspek at gmail dot com  2007-12-09 18:52 -------
Hasn't the comment from hjl@lucon.org been implemented?

AFAIK <ext/hash_set> works in 4.3 and generates the deprecation warning.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[olafvdspek at gmail dot com]

------- Comment #4 from olafvdspek at gmail dot com  2007-12-09 18:56 -------
I reported the bug below to Debian. I'm not that familiar with those headers,
but I think it'd be a good idea to not deprecate them until the replacements
have been available for quite a while.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455199

Package: g++-4.3
Version: 4.3-20071130-1
Severity: normal

Hi,

<ext/hash_set> is deprecated in 4.3, but it's replacement, <unordered_set>
doesn't appeart to be available in 4.2.
Using <unordered_set> doesn't sound like a good plan (at the moment), so
wouldn't it make sense to postpone the deprecation until it's replacement has
been available for some time?
The extreme would be to wait until 4.3 is in oldstable.

Greetings,

Olaf


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[pcarlini at suse dot de]

------- Comment #5 from pcarlini at suse dot de  2007-12-09 19:49 -------
(In reply to comment #4)
> <ext/hash_set> is deprecated in 4.3, but it's replacement, <unordered_set>
> doesn't appeart to be available in 4.2.

Just use <tr1/unordered_set>


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[bkoz at gcc dot gnu dot org]

------- Comment #6 from bkoz at gcc dot gnu dot org  2007-12-11 22:21 -------

HJ: this and 33831 are the same thing. I would appreciate it if you could
either clarify why you think they are separate, or close one of them. I suggest
closing 33832.

This PR I will treat as "How HJ can fix eon in SPEC 2000". I suspect this is
what motivated this bug report.

Here's the bit from SPEC, courtesy of Vlad.

/home/cygnus/vmakarov/perf/sbox/gcc/local.spec2000.x86_64/inst.toolbox/bin/g++
-c -o ggCoverageSolidTexture.o  -DHAS_ERRLIST -DSPEC_STDCPP
-DFMAX_IS_DOUBLE -DUSE_STRERROR -Wno-deprecated -DSPEC_CPU2000_LP64
-fpermissive     -I. -DNDEBUG     -O2 -mtune=generic
ggCoverageSolidTexture.cc

Ie:

1) -Wno-deprecated
2) -fpermissive

Fixing -Wno-deprecated would have been/is still easy.

change
#include <iostream.h>

to

# include <iostream>
using namespace std;

Yay! Safe for the millennium.

I don't know what it would take to fix -fpermissive.

You can find more information about this, and an autoconf macro that tests for
this, here:


http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/backwards_compatibility.html

Look for "Pre-ISO headers moved to backwards or removed"

best,
benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API

[hjl at lucon dot org]

------- Comment #7 from hjl at lucon dot org  2007-12-11 23:00 -------
This one is for "moved" header files. One can include different header files
for gcc 4.3. PR 33831 is for "removed" header files. I don't know if gcc
4.3 provides the identical functionality as the old one. One may needs more
than including different header files for gcc 4.3.

BTW, not all applications use autoconf.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] hash_set moved to backwards

[bkoz at gcc dot gnu dot org]

------- Comment #8 from bkoz at gcc dot gnu dot org  2007-12-11 23:21 -------

Changed the tile to something unique.


-- 

bkoz at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Can't tell gcc 4.3 libstdc++|hash_set moved to backwards
                   |API from gcc 4.2 libstdc++  |
                   |API                         |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] hash_set moved to backwards

[bkoz at gcc dot gnu dot org]

------- Comment #9 from bkoz at gcc dot gnu dot org  2007-12-11 23:25 -------

HJ:

"I don't know if gcc 4.3 provides the identical functionality as the old one."

We've all answered this multiple times by now. Quick answer: yes.

See #5. 

-benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] hash_set moved to backwards

[olafvdspek at gmail dot com]

------- Comment #10 from olafvdspek at gmail dot com  2007-12-12 12:29 -------
> Just use <tr1/unordered_set>

It'd be nice if the deprecated warning mentioned that file.


-- 

olafvdspek at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olafvdspek at gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] hash_set moved to backwards

[bkoz at gcc dot gnu dot org]

------- Comment #11 from bkoz at gcc dot gnu dot org  2008-02-18 00:18 -------

I'd like to close this (since ext/hash_map and ext/hash_set exist now, and
merge the bits about better error messages into 34015.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832

[Bug libstdc++/33832] hash_set moved to backwards

[rguenth at gcc dot gnu dot org]

------- Comment #12 from rguenth at gcc dot gnu dot org  2008-03-14 17:03 -------
I declare this fixed.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33832