public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/47106] -fcompare-debug failure (length) with -fpartial-inlining -flto -fconserve-stack
Date: Mon, 21 Feb 2011 14:22:00 -0000 [thread overview]
Message-ID: <bug-47106-4-4giOiOGEv4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47106-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47106
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |danglin at gcc dot gnu.org
--- Comment #16 from John David Anglin <danglin at gcc dot gnu.org> 2011-02-21 13:44:58 UTC ---
Executing on host: /test/gnu/gcc/objdir/gcc/testsuite/g++/../../g++
-B/test/gnu/
gcc/objdir/gcc/testsuite/g++/../../
/test/gnu/gcc/gcc/gcc/testsuite/g++.dg/debug
/pr47106.C -nostdinc++
-I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/libstdc++-v
3/include/hppa2.0w-hp-hpux11.11
-I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/lib
stdc++-v3/include -I/test/gnu/gcc/gcc/libstdc++-v3/libsupc++
-I/test/gnu/gcc/gcc
/libstdc++-v3/include/backward -I/test/gnu/gcc/gcc/libstdc++-v3/testsuite/util
-
fmessage-length=0 -gstabs1 -O -fpartial-inlining -flto -fconserve-stack
-fcompar
e-debug -S -o pr47106.s (timeout = 300)
cc1plus: error: LTO support has not been enabled in this configuration
compiler exited with status 1
output is:
cc1plus: error: LTO support has not been enabled in this configuration
FAIL: g++.dg/debug/pr47106.C -gstabs1 (test for excess errors)
Excess errors:
cc1plus: error: LTO support has not been enabled in this configuration
next prev parent reply other threads:[~2011-02-21 13:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 11:41 [Bug debug/47106] New: " zsojka at seznam dot cz
2010-12-30 20:09 ` [Bug debug/47106] " aoliva at gcc dot gnu.org
2010-12-30 20:15 ` aoliva at gcc dot gnu.org
2011-01-21 15:17 ` aoliva at gcc dot gnu.org
2011-01-21 15:40 ` aoliva at gcc dot gnu.org
2011-01-21 22:36 ` aoliva at gcc dot gnu.org
2011-01-31 8:07 ` aoliva at gcc dot gnu.org
2011-01-31 11:55 ` aoliva at gcc dot gnu.org
2011-02-02 5:44 ` aoliva at gcc dot gnu.org
2011-02-02 6:18 ` aoliva at gcc dot gnu.org
2011-02-02 6:28 ` aoliva at gcc dot gnu.org
2011-02-15 18:36 ` aoliva at gcc dot gnu.org
2011-02-15 18:37 ` aoliva at gcc dot gnu.org
2011-02-15 18:37 ` aoliva at gcc dot gnu.org
2011-02-15 18:38 ` aoliva at gcc dot gnu.org
2011-02-17 16:24 ` hubicka at gcc dot gnu.org
2011-02-21 14:22 ` danglin at gcc dot gnu.org [this message]
2011-02-21 16:06 ` jakub at gcc dot gnu.org
2011-02-23 0:47 ` aoliva 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-47106-4-4giOiOGEv4@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).