public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-51785-4-7al5SzR76W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51785-4@http.gcc.gnu.org/bugzilla/> 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..
next prev parent reply other threads:[~2012-02-28 16:43 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-07 15:31 [Bug c++/51785] New: " drepper.fsp at gmail dot com 2012-01-07 19:06 ` [Bug c++/51785] " marc.glisse at normalesup dot org 2012-01-10 22:25 ` vries at gcc dot gnu.org 2012-01-11 13:00 ` vries at gcc dot gnu.org 2012-01-11 13:26 ` [Bug libstdc++/51785] " redi at gcc dot gnu.org 2012-01-11 13:50 ` marc.glisse at normalesup dot org 2012-02-05 20:34 ` jakub at gcc dot gnu.org 2012-02-05 21:00 ` redi at gcc dot gnu.org 2012-02-05 21:27 ` redi at gcc dot gnu.org 2012-02-28 14:46 ` ramana at gcc dot gnu.org 2012-02-28 15:26 ` joseph at codesourcery dot com 2012-02-28 15:38 ` paolo.carlini at oracle dot com 2012-02-28 15:51 ` marc.glisse at normalesup dot org 2012-02-28 15:54 ` jakub at gcc dot gnu.org 2012-02-28 16:14 ` ramana at gcc dot gnu.org 2012-02-28 16:25 ` jakub at gcc dot gnu.org 2012-02-28 17:07 ` paolo.carlini at oracle dot com [this message] 2012-02-28 17:08 ` joseph at codesourcery dot com 2012-02-28 18:46 ` paolo.carlini at oracle dot com 2012-03-01 0:23 ` bkoz at gcc dot gnu.org 2012-03-01 13:31 ` jakub at gcc dot gnu.org 2012-03-01 13:45 ` rguenth at gcc dot gnu.org 2012-03-01 13:51 ` redi at gcc dot gnu.org 2012-03-02 6:32 ` bkoz at gcc dot gnu.org 2012-03-02 7:14 ` bkoz at gcc dot gnu.org 2012-03-02 7:30 ` jakub at gcc dot gnu.org 2012-03-09 22:15 ` jsm28 at gcc dot gnu.org 2012-03-09 23:49 ` paolo.carlini at oracle dot com 2021-07-18 18:40 ` pinskia at gcc dot gnu.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=bug-51785-4-7al5SzR76W@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).