public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gregod@cs.rpi.edu
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/5611: (Unsigned) long long I/O unsupported on FreeBSD 3.4
Date: Wed, 06 Feb 2002 06:36:00 -0000 [thread overview]
Message-ID: <20020206142959.16112.qmail@sources.redhat.com> (raw)
>Number: 5611
>Category: libstdc++
>Synopsis: (Unsigned) long long I/O unsupported on FreeBSD 3.4
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 06 06:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Doug Gregor
>Release: gcc-3.0.3
>Organization:
>Environment:
FreeBSD 3.4
>Description:
_GLIBCPP_USE_LONG_LONG is left undefined because the system C library does not support strtoll and strtoull, and therefore I/O for (unsigned) long long values is unsupported by libstdc++.
GCC 2.95.x has I/O support for (unsigned) long long.
>How-To-Repeat:
configure on a system without strtoll/strtoull available
>Fix:
Port the string->integer conversion routines from glibc to be used when the C library does not support strtoll/strtoull.
I'd be willing to help if this is deemed the right way to go.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-02-06 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 6:36 gregod [this message]
2002-04-04 12:13 bkoz
2003-03-26 6:36 ljrittle
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=20020206142959.16112.qmail@sources.redhat.com \
--to=gregod@cs.rpi.edu \
--cc=gcc-gnats@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).