public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/38776] gcc 4.4.0 20090109 - Configure with "--enable-coverage=noopt" breaks build Date: Sun, 11 Jan 2009 02:50:00 -0000 [thread overview] Message-ID: <20090111025000.14710.qmail@sourceware.org> (raw) In-Reply-To: <bug-38776-13830@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1997 bytes --] ------- Comment #5 from rob1weld at aol dot com 2009-01-11 02:50 ------- Breaks again here: /usr/share/src/gcc_build/./prev-gcc/xgcc -B/usr/share/src/gcc_build/./prev-gcc/ -B/usr/local/i386-pc-solaris2.11/bin/ -c -g -O2 -fprofile-use -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -DHAVE_CONFIG_H -I. -I. -I../../gcc_trunk/gcc -I../../gcc_trunk/gcc/. -I../../gcc_trunk/gcc/../include -I./../intl -I../../gcc_trunk/gcc/../libcpp/include -I../../gcc_trunk/gcc/../libdecnumber -I../../gcc_trunk/gcc/../libdecnumber/dpd -I../libdecnumber -DCLOOG_PPL_BACKEND -fexceptions ../../gcc_trunk/gcc/varasm.c -o varasm.o ../../gcc_trunk/gcc/varasm.c: In function default_elf_asm_named_section: ../../gcc_trunk/gcc/varasm.c:6791: error: coverage mismatch for function default_elf_asm_named_section while reading counter arcs ../../gcc_trunk/gcc/varasm.c:6791: note: number of counters is 18 instead of 22 ../../gcc_trunk/gcc/varasm.c:6791: error: coverage mismatch for function default_elf_asm_named_section while reading counter indirect_call ../../gcc_trunk/gcc/varasm.c:6791: note: number of counters is 0 instead of 3 ../../gcc_trunk/gcc/varasm.c: In function default_function_rodata_section: ../../gcc_trunk/gcc/varasm.c:6791: error: coverage mismatch for function default_function_rodata_section while reading counter arcs ../../gcc_trunk/gcc/varasm.c:6791: note: number of counters is 10 instead of 12 gmake[3]: *** [varasm.o] Error 1 gmake[3]: Leaving directory `/usr/share/src/gcc_build/gcc' gmake[2]: *** [all-stagefeedback-gcc] Error 2 gmake[2]: Leaving directory `/usr/share/src/gcc_build' gmake[1]: *** [stagefeedback-bubble] Error 2 gmake[1]: Leaving directory `/usr/share/src/gcc_build' gmake: *** [all] Error 2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38776
next prev parent reply other threads:[~2009-01-11 2:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-09 8:16 [Bug bootstrap/38776] New: " rob1weld at aol dot com 2009-01-09 8:27 ` [Bug bootstrap/38776] " rob1weld at aol dot com 2009-01-09 17:45 ` rob1weld at aol dot com 2009-01-09 20:42 ` pinskia at gcc dot gnu dot org 2009-01-09 21:49 ` rob1weld at aol dot com 2009-01-10 5:47 ` rob1weld at aol dot com 2009-01-11 2:50 ` rob1weld at aol dot com [this message] 2009-01-13 0:32 ` pinskia at gcc dot gnu dot org 2009-01-13 15:17 ` rob1weld at aol dot com
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=20090111025000.14710.qmail@sourceware.org \ --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: linkBe 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).