public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tot@trema.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/2992: 3.0: string functions not always accessible
Date: Tue, 29 May 2001 07:26:00 -0000	[thread overview]
Message-ID: <20010529141837.7325.qmail@sourceware.cygnus.com> (raw)

>Number:         2992
>Category:       libstdc++
>Synopsis:       3.0: string functions not always accessible
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue May 29 07:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Teemu Torma
>Release:        gcc version 3.0 20010525 (prerelease)
>Organization:
>Environment:
i686-pc-linux-gnu (RedHat 6.2)
>Description:
Regression from 2.95.2.

Accessibility of standard C string functions (strlen etc) 
depends on the include file order.

If <string.h> is included before <cstring>, everything
works fine, but if after, the compiler says that functions
are undeclared.

It seems to happen only if the code using the string 
functions is in a namespace, like in the example code.

>How-To-Repeat:
$ /usr/local/gcc3/bin/g++ -c -v bug.cc
Reading specs from /usr/local/gcc3/lib/gcc-lib/i686-pc-linux-gnu/3.0/specs
Configured with: ../gcc-3.0-branch/configure --with-gcc-version-trigger=/work/tot/gcc/3.0/gcc-3.0-branch/gcc/version.c --host=i686-pc-linux-gnu --prefix=/usr/local/gcc3 --enable-version-specific-runtime-libs --enable-long-long
Thread model: single
gcc version 3.0 20010525 (prerelease)
 /usr/local/gcc3/lib/gcc-lib/i686-pc-linux-gnu/3.0/cc1plus -v -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=0 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__STDC_HOSTED__=1 -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i686__ -D__tune_pentiumpro__ bug.cc -D__GNUG__=3 -D_GNU_SOURCE -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase bug.cc -version -o /tmp/ccpHgH6g.s
GNU CPP version 3.0 20010525 (prerelease) (cpplib) (i386 Linux/ELF)
GNU C++ version 3.0 20010525 (prerelease) (i686-pc-linux-gnu)
	compiled by GNU C version 3.0 20010525 (prerelease).
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/gcc3/lib/gcc-lib/i686-pc-linux-gnu/3.0/include/g++
 /usr/local/gcc3/lib/gcc-lib/i686-pc-linux-gnu/3.0/include/g++/i686-pc-linux-gnu
 /usr/local/gcc3/lib/gcc-lib/i686-pc-linux-gnu/3.0/include/g++/backward
 /usr/local/include
 /usr/local/gcc3/lib/gcc-lib/i686-pc-linux-gnu/3.0/include
 /usr/local/gcc3/i686-pc-linux-gnu/include
 /usr/include
End of search list.
bug.cc: In function `int bar::foo(const char*)':
bug.cc:8: `strlen' undeclared (first use this function)
bug.cc:8: (Each undeclared identifier is reported only once for each function 
   it appears in.)
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="bug.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug.cc"

I2luY2x1ZGUgPGNzdHJpbmc+CiNpbmNsdWRlIDxzdHJpbmcuaD4KCm5hbWVzcGFjZSBiYXIKewog
IGludCBmb28gKGNvbnN0IGNoYXIgKngpCiAgewogICAgcmV0dXJuIHN0cmxlbiAoeCk7CiAgfQp9
Owo=


             reply	other threads:[~2001-05-29  7:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  7:26 tot [this message]
2001-06-07 15:26 mmitchel
2001-06-08 16:05 bkoz
2001-06-09 23:51 bkoz

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=20010529141837.7325.qmail@sourceware.cygnus.com \
    --to=tot@trema.com \
    --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).