public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nicolas.cavallari at lri dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58393] Please relax feature check for std::to_string and std::sto* for uClibc
Date: Thu, 03 Jul 2014 12:37:00 -0000	[thread overview]
Message-ID: <bug-58393-4-1yYPvnwjpo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58393-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58393

nicolas.cavallari at lri dot fr changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #30800|0                           |1
        is obsolete|                            |

--- Comment #4 from nicolas.cavallari at lri dot fr ---
Created attachment 33060
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33060&action=edit
7 patches for being more specific with feature checks, in mbox format.

Following Paolo's comment, i made some other patches a while ago, using more
specific feature checks everywhere.  The only part where _GLIBCXX_USE_C99 is
still needed is when determining whether the time functions allows one or two
leap seconds.

However, my attemps to run the testsuite were always met with frustration and
undeterministic results, so i delayed it and kept working around the problem in
my programs.

I attach my untested patches here. Maybe i'll fight with the testsuite again,
maybe not.


      parent reply	other threads:[~2014-07-03 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 15:58 [Bug libstdc++/58393] New: " nicolas.cavallari at lri dot fr
2013-09-11 16:32 ` [Bug libstdc++/58393] " paolo.carlini at oracle dot com
2014-07-02 21:59 ` thomas.petazzoni@free-electrons.com
2014-07-02 23:46 ` redi at gcc dot gnu.org
2014-07-03 12:37 ` nicolas.cavallari at lri dot fr [this message]

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-58393-4-1yYPvnwjpo@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: 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).