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 target/51252] New: FAIL: c-c++-common/tm/freq.c (internal compiler error)
Date: Mon, 21 Nov 2011 02:54:00 -0000 [thread overview]
Message-ID: <bug-51252-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51252
Bug #: 51252
Summary: FAIL: c-c++-common/tm/freq.c (internal compiler error)
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: danglin@gcc.gnu.org
Host: hppa2.0w-hp-hpux11.11
Target: hppa2.0w-hp-hpux11.11
Build: hppa2.0w-hp-hpux11.11
Executing on host: /test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc/
/te
st/gnu/gcc/gcc/gcc/testsuite/c-c++-common/tm/freq.c -fgnu-tm -O -S -o
freq.s (timeout = 300)
/test/gnu/gcc/gcc/gcc/testsuite/c-c++-common/tm/freq.c:14:1: internal compiler
e
rror: in default_no_named_section, at varasm.c:6295Please submit a full bug
report,with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.compiler exited with status
1
output is:
/test/gnu/gcc/gcc/gcc/testsuite/c-c++-common/tm/freq.c:14:1: internal compiler
e
rror: in default_no_named_section, at varasm.c:6295
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
FAIL: c-c++-common/tm/freq.c (internal compiler error)
FAIL: c-c++-common/tm/freq.c (test for excess errors)
-bash-3.2$ ./xgcc -B./ -v
Reading specs from ./specs
COLLECT_GCC=./xgcc
COLLECT_LTO_WRAPPER=./lto-wrapper
Target: hppa2.0w-hp-hpux11.11
Configured with: ../gcc/configure --with-gnu-as --with-as=/opt/gnu/bin/as
--enable-shared --with-local-prefix=/opt/gnu --prefix=/opt/gnu/gcc/gcc-4.7
--with-gmp=/opt/gnu/gcc/gmp --enable-threads=posix --enable-debug=no
--disable-nls --disable-lto --without-cloog --without-ppl
--enable-languages=c,c++,objc,fortran,java,ada,obj-c++
Thread model: posix
gcc version 4.7.0 20111116 (experimental) [trunk revision 181404] (GCC)
Target doesn't support named sections.
next reply other threads:[~2011-11-21 2:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 2:54 danglin at gcc dot gnu.org [this message]
2011-11-27 20:55 ` [Bug target/51252] " danglin at gcc dot gnu.org
2011-12-16 17:51 ` [Bug middle-end/51252] " ro at gcc dot gnu.org
2011-12-16 17:56 ` ro at gcc dot gnu.org
2011-12-16 18:05 ` rth at gcc dot gnu.org
2011-12-16 18:22 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-12-17 1:18 ` dave.anglin at bell dot net
2011-12-19 0:10 ` dave.anglin at bell dot net
2011-12-23 2:03 ` danglin at gcc dot gnu.org
2011-12-23 2:11 ` danglin at gcc dot gnu.org
2012-01-09 15:56 ` patrick.marlier at gmail dot com
2012-01-09 18:45 ` dave.anglin at bell dot net
2012-01-10 18:47 ` ro at gcc dot gnu.org
2012-03-22 8:59 ` rguenth at gcc dot gnu.org
2012-07-02 12:59 ` rguenth at gcc dot gnu.org
2015-02-13 0:25 ` rth 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-51252-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).