From: Jan Hubicka <hubicka@ucw.cz>
To: Bernardo Innocenti <bernie@develer.com>
Cc: gcc@gcc.gnu.org
Subject: Re: make profiledbootstrap broken?
Date: Sun, 12 Oct 2003 00:29:00 -0000 [thread overview]
Message-ID: <20031011193801.GF14661@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <3F877658.7050307@develer.com>
> Hello,
>
> is it just me doing something wrong or the profiledbootstrap
> feature is currently broken in mainline?
>
> It seems some source files are missing the accompaning .gcda file:
>
>
> stage1/xgcc -Bstage1/
> -B/usr/local/src/gcc_combined/i386-linux-HEAD-install/i686-pc-linux-gnu/bin/ -c -g -O2 -fbranch-probabilities -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Werror -fno-common -DHAVE_CONFIG_H -I. -I. -I../../combined-HEAD/gcc -I../../combined-HEAD/gcc/. -I../../combined-HEAD/gcc/../include ../../combined-HEAD/gcc/resource.c -o resource.o
> ../../combined-HEAD/gcc/resource.c: In function
> `clear_hashed_info_for_insn':
>
> ../../combined-HEAD/gcc/resource.c:1280: warning: file resource.gcda not
> found, execution counts assumed to be zero
The problem is that Makefile now incorrectly pass -Werror for
profilestage flags. This is fixed by patch I sent some time ago but it
wasn't reviewed yet. You may work around by disabling -Werror in
configure (don't remmber the name of flag)
Honza
> make[2]: *** [resource.o] Error 1
> make[2]: Leaving directory
> `/usr/local/src/gcc_combined/i386-linux-HEAD-build/gcc'
> make[1]: *** [stagefeedback_build] Error 2
> make[1]: Leaving directory
> `/usr/local/src/gcc_combined/i386-linux-HEAD-build/gcc'
> make: *** [profiledbootstrap] Error 2
>
>
> --
> // Bernardo Innocenti - Develer S.r.l., R&D dept.
> \X/ http://www.develer.com/
>
> Please don't send Word attachments -
> http://www.gnu.org/philosophy/no-word-attachments.html
>
>
prev parent reply other threads:[~2003-10-11 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 6:05 Bernardo Innocenti
2003-10-11 6:11 ` Andrew Pinski
2003-10-11 11:08 ` Bernardo Innocenti
2003-10-12 0:29 ` Jan Hubicka [this message]
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=20031011193801.GF14661@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=bernie@develer.com \
--cc=gcc@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).