public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33832] Can't tell gcc 4.3 libstdc++ API from gcc 4.2 libstdc++ API
Date: Tue, 11 Dec 2007 22:22:00 -0000	[thread overview]
Message-ID: <20071211222157.23182.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33832-682@http.gcc.gnu.org/bugzilla/>



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


  parent reply	other threads:[~2007-12-11 22:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 15:30 [Bug libstdc++/33832] New: " hjl at lucon dot org
2007-10-21 21:45 ` [Bug libstdc++/33832] " hjl at lucon dot org
2007-10-31 21:35 ` bkoz at gcc dot gnu dot org
2007-12-08 23:24 ` pinskia at gcc dot gnu dot org
2007-12-09 18:52 ` olafvdspek at gmail dot com
2007-12-09 18:56 ` olafvdspek at gmail dot com
2007-12-09 19:50 ` pcarlini at suse dot de
2007-12-11 22:22 ` bkoz at gcc dot gnu dot org [this message]
2007-12-11 23:00 ` hjl at lucon dot org
2007-12-11 23:21 ` [Bug libstdc++/33832] hash_set moved to backwards bkoz at gcc dot gnu dot org
2007-12-11 23:25 ` bkoz at gcc dot gnu dot org
2007-12-12 12:30 ` olafvdspek at gmail dot com
2008-02-18  0:18 ` bkoz at gcc dot gnu dot org
2008-03-14 17:03 ` rguenth at gcc dot gnu dot org

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=20071211222157.23182.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).