public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "blair at orcaware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/15137] make profiledbootstrap fails on Cygwin
Date: Sun, 25 Apr 2004 23:57:00 -0000	[thread overview]
Message-ID: <20040425224401.4565.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040425190632.15137.blair@orcaware.com>


------- Additional Comments From blair at orcaware dot com  2004-04-25 22:43 -------
The same failure occurs without setting any CFLAGS:

bzcat.exe gcc-3.4.0.tar.bz2 | tar xvf -
mkdir g
cd g
env CC=/opt/i386-cygwin/gcc/bin/gcc ../gcc-3.4.0/configure \
--prefix=/tmp/gcc3.4.0 --enable-languages="c,c++" --verbose \
--enable-shared --enable-threads --with-system-zlib \
--disable-win32-registry
make profiledbootstrap

Here's the output:

stage1/xgcc.exe -Bstage1/ -B/tmp/gcc3.4.0/i686-pc-cygwin/bin/ -c   -g -O2 -
fprofile-use -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prototypes -pedantic -Wno-long-long -Wold-style-definition     -
DHAVE_CONFIG_H    -I. -I. -I../../gcc-3.4.0/gcc -I../../gcc-3.4.0/gcc/. -
I../../gcc-3.4.0/gcc/../include  ../../gcc-3.4.0/gcc/cppinit.c -o cppinit.o
stage1/xgcc.exe -Bstage1/ -B/tmp/gcc3.4.0/i686-pc-cygwin/bin/ -c   -g -O2 -
fprofile-use -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prototypes -pedantic -Wno-long-long -Wold-style-definition     -
DHAVE_CONFIG_H    -I. -I. -I../../gcc-3.4.0/gcc -I../../gcc-3.4.0/gcc/. -
I../../gcc-3.4.0/gcc/../include  ../../gcc-3.4.0/gcc/cppcharset.c -o 
cppcharset.o
stage1/xgcc.exe -Bstage1/ -B/tmp/gcc3.4.0/i686-pc-cygwin/bin/ -c   -g -O2 -
fprofile-use -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prototypes -pedantic -Wno-long-long -Wold-style-definition     -
DHAVE_CONFIG_H    -I. -I. -I../../gcc-3.4.0/gcc -I../../gcc-3.4.0/gcc/. -
I../../gcc-3.4.0/gcc/../include  ../../gcc-3.4.0/gcc/hashtable.c -o hashtable.o
../../gcc-3.4.0/gcc/hashtable.c: In function `ht_lookup':
../../gcc-3.4.0/gcc/hashtable.c:165: error: corrupted profile info: number of 
executions for edge 0-1 thought to be 8962734
../../gcc-3.4.0/gcc/hashtable.c:165: error: corrupted profile info: number of 
executions for edge 0-2 thought to be -1
make[2]: *** [hashtable.o] Error 1
make[2]: Leaving directory `/cygdrive/c/Blair/Cygwin/Code/g/g/gcc'
make[1]: *** [stagefeedback_build] Error 2
make[1]: Leaving directory `/cygdrive/c/Blair/Cygwin/Code/g/g/gcc'
make: *** [profiledbootstrap] Error 2

Best,
Blair

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15137


  parent reply	other threads:[~2004-04-25 22:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-25 20:09 [Bug bootstrap/15137] New: " blair at orcaware dot com
2004-04-25 20:13 ` [Bug bootstrap/15137] " blair at orcaware dot com
2004-04-25 20:17 ` blair at orcaware dot com
2004-04-25 20:39 ` blair at orcaware dot com
2004-04-25 20:39 ` pinskia at gcc dot gnu dot org
2004-04-25 23:57 ` blair at orcaware dot com [this message]
2004-07-11  4:44 ` blair at orcaware dot com
2004-07-15 18:53 ` pinskia at gcc dot gnu dot org
2004-10-07  9:27 ` giovannibajo at libero dot it
2005-01-06  1:04 ` pinskia at gcc dot gnu dot 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=20040425224401.4565.qmail@sources.redhat.com \
    --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).