public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: gdr@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/1773: __cplusplus defined to 1, should be 199711L
Date: Thu, 13 Mar 2003 00:26:00 -0000	[thread overview]
Message-ID: <20030313002600.18423.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/1773; it has been noted by GNATS.

From: Benjamin Kosnik <bkoz@redhat.com>
To: neroden@twcny.rr.com
Cc: gcc-gnats@gcc.gnu.org, Jens.Maurer@gmx.net, gcc@gcc.gnu.org,
   gcc-bugs@gcc.gnu.org, gdr@gcc.gnu.org, pme@sourceware.cygnus.com,
   gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/1773: __cplusplus defined to 1, should be 199711L
Date: Wed, 12 Mar 2003 18:23:59 -0600

 On Wed, 12 Mar 2003 16:32:03 -0500
 Nathanael Nerode <neroden@twcny.rr.com> wrote:
 
 >This is a very old report.  What's the status now?  It was suspended because 
 >the standard conforming value for __cplusplus broke libstdc++-v3 on many 
 >platforms.  libstdc++-v3 and the C++ front end have both undergone dramatic 
 >changes and improvements.  Can this be fixed now?
 
 Sadly, this can't be fixed at the moment, at least on most platforms.
 For cross compilers using newlib, this was fixed some time back with the
 --enable-headers=c work done at the time of the QNX port. That is not
 the default configuration, however.
 
 One of the things blocking this is hardware, ie real access to
 up-to-date sun hardware with sunpro tools so I can see what is going on.
 The other issue is time: I don't have enough of it, and this is
 something I consider a lower priority than other issues. There were some
 patches in glibc-2.3.x that went in that may allow a more elegant
 solution for linux, but that work is not finished.
 
 best,
 benjamin
 


             reply	other threads:[~2003-03-13  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  0:26 Benjamin Kosnik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 21:36 Nathanael Nerode

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=20030313002600.18423.qmail@sources.redhat.com \
    --to=bkoz@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gdr@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).