From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-384797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 12849 invoked by alias); 28 Feb 2012 16:43:27 -0000
Received: (qmail 12809 invoked by uid 22791); 28 Feb 2012 16:43:25 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Feb 2012 16:43:12 +0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51785] gets not anymore declared
Date: Tue, 28 Feb 2012 17:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51785-4-7al5SzR76W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51785-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-02/txt/msg02731.txt.bz2

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

--- Comment #16 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-02-28 16:42:55 UTC ---
I suppose that post 4.7.0 we have to revisit this issue anyway, because C++11
definitely wants to declare std::gets, irrespective of C11. I'm wondering if it
would be possible to just take this into account in <stdio.h>, I seem to
remember that the glibc headers in a few places already use __cplusplus, right?
We also have the __CORRECT_ISO_CPP_STRING_H_PROTO story as an example of
interaction between glibc and C++.

That said, for 4.7.0, I think that in any case we want: 1- To fully run the
testsuite on a GNU/Linux system using glibc2.15; 2- Convince ourselves that
whatever we do in the C++ library is not going to interact badly with further
tweaks at the glibc level..