public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "maxime.boissonneault at calculquebec dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/61101] New: snprintf not part of std
Date: Wed, 07 May 2014 18:57:00 -0000 [thread overview]
Message-ID: <bug-61101-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61101
Bug ID: 61101
Summary: snprintf not part of std
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: maxime.boissonneault at calculquebec dot ca
Created attachment 32755
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32755&action=edit
The output with -save-temps
- the exact version of GCC;
GCC 4.8.2
- the system type;
CentOS 6.5
- the options given when GCC was configured/built;
../${SRCDIR}/configure CFLAGS="$FLAGS" CXXFLAGS="$FLAGS" \
LDFLAGS="-L$PREFIX/lib" --prefix=$PREFIX \
--with-arch=native --with-pkgversion=$VERSION-colosse \
--enable-languages=c,c++,java,fortran,go --enable-shared \
--enable-static --enable-threads=posix --enable-multilib \
--enable-bootstrap --with-gmp=$PREFIX --with-mpfr=$PREFIX --with-mpc=$PREFIX
\
--with-system-zlib
- the complete command line that triggers the bug;
g++ test.cpp -std=c++11
- the compiler output (error messages, warnings, etc.); and
the preprocessed file (*.i*) that triggers the bug, generated by adding
-save-temps to the complete compilation command, or, in the case of a bug
report for the GNAT front end, a complete set of source files (see below).
test.cpp: In function ‘int main()’:
test.cpp:5:2: erreur: ‘snprintf’ is not a member of ‘std’
std::snprintf(test, 10, "%f", 2.);
^
test.cpp:5:2: note: suggested alternative:
In file included from
/software6/compilers/gcc/4.8.2/include/c++/4.8.2/cstdio:42:0,
from test.cpp:1:
/usr/include/stdio.h:385:12: note: ‘snprintf’
extern int snprintf (char *__restrict __s, size_t __maxlen,
>From gcc-bugs-return-450888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 07 19:01:05 2014
Return-Path: <gcc-bugs-return-450888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10030 invoked by alias); 7 May 2014 19:01:05 -0000
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
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9973 invoked by uid 48); 7 May 2014 19:01:00 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61026] sh-rtems4.11 build of 4.9.0 fails on FreeBSD 10 c++ (clang).
Date: Wed, 07 May 2014 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: olegendo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61026-4-n4yYdt8JA2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61026-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61026-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg00580.txt.bz2
Content-length: 367
http://gcc.gnu.org/bugzilla/show_bug.cgi?ida026
--- Comment #10 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Sorry for the trouble, but Joseph has a point here ...
http://gcc.gnu.org/ml/gcc-patches/2014-05/msg00414.html
Could you guys please try moving the problematic header includes in sh.c below
the #include "config.h" and report your findings? Thanks.
next reply other threads:[~2014-05-07 18:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 18:57 maxime.boissonneault at calculquebec dot ca [this message]
2014-05-07 21:34 ` [Bug libstdc++/61101] " redi at gcc dot gnu.org
2014-05-07 21:41 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:32 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:34 ` redi at gcc dot gnu.org
2014-05-07 22:38 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:41 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:42 ` paolo.carlini at oracle dot com
2014-05-07 22:47 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:50 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:55 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 22:56 ` paolo.carlini at oracle dot com
2014-05-07 23:01 ` paolo.carlini at oracle dot com
2014-05-07 23:04 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 23:10 ` paolo.carlini at oracle dot com
2014-05-07 23:16 ` maxime.boissonneault at calculquebec dot ca
2014-05-07 23:19 ` maxime.boissonneault at calculquebec dot ca
2014-05-08 0:00 ` redi at gcc dot gnu.org
2014-05-08 0:50 ` redi at gcc dot gnu.org
2014-05-08 19:52 ` maxime.boissonneault at calculquebec dot ca
2014-05-08 20:02 ` redi 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-61101-4@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).