public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yuri at tsoft dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61652] New: Option --enable-libstdcxx-debug doesn't pass debug options to libstdc++.so
Date: Mon, 30 Jun 2014 00:28:00 -0000 [thread overview]
Message-ID: <bug-61652-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61652
Bug ID: 61652
Summary: Option --enable-libstdcxx-debug doesn't pass debug
options to libstdc++.so
Product: gcc
Version: 4.8.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: yuri at tsoft dot com
Based on documentation here
https://gcc.gnu.org/onlinedocs/libstdc++/manual/debug.html I configured gcc to
build a debug version of libstdc++.so:
$ ../src/configure --prefix=/opt/gcc/4.8.2/ --enable-libstdcxx-debug
--enable-libstdcxx-debug-flags='-g3 -O0'
$ gmake
It did build another version of libstdc++.so with different size under
lib/debug/, but both of them have local variables optimized away.
I am interested in ../src/libstdc++-v3/libsupc++/dyncast.cc, touching it and
rebuilding shows that -O0 hasn't been passed to the compile command, and it
builds with -O2.
Building gcc-4.8.2 on FreeBSD-10
next reply other threads:[~2014-06-30 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 0:28 yuri at tsoft dot com [this message]
2015-03-25 18:08 ` [Bug c++/61652] Option --enable-libstdcxx-debug doesn't pass debug compile " redi at gcc dot gnu.org
2015-03-25 18:28 ` [Bug c++/61652] Option --enable-libstdcxx-debug doesn't build debug version of libsupc++.so 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-61652-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).