From: Joseph Myers <joseph@codesourcery.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
<gcc-patches@gcc.gnu.org>
Subject: Re: Reorgnanization of profile count maintenance code, part 1
Date: Mon, 05 Jun 2017 15:13:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706051512110.19349@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20170604172130.GA48489@kam.mff.cuni.cz>
I'm seeing a build failure for mips64-linux-gnu:
In file included from
/scratch/jmyers/glibc-bot/src/gcc/gcc/config/mips/frame-header-opt.c:35:0:
/scratch/jmyers/glibc-bot/src/gcc/gcc/cfg.h:106:64: error: 'profile_count' has not been declared
extern void update_bb_profile_for_threading (basic_block, int, profile_count, edge);
^
/scratch/jmyers/glibc-bot/src/gcc/gcc/cfg.h:111:11: error: 'profile_count' has not been declared
profile_count, profile_count);
^
/scratch/jmyers/glibc-bot/src/gcc/gcc/cfg.h:111:26: error: 'profile_count' has not been declared
profile_count, profile_count);
^
/scratch/jmyers/glibc-bot/src/gcc/gcc/config/mips/t-mips:25: recipe for target 'frame-header-opt.o' failed
make[3]: *** [frame-header-opt.o] Error 1
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-05 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 11:36 Jan Hubicka
2017-06-03 18:51 ` Bernhard Reutner-Fischer
2017-06-04 17:21 ` Jan Hubicka
2017-06-05 15:13 ` Joseph Myers [this message]
2017-06-05 15:16 ` Jan Hubicka
2017-06-05 15:37 ` Jan Hubicka
2017-06-05 18:38 ` Andrew Pinski
2017-06-06 5:57 ` Jason Merrill
2017-06-06 8:00 ` Jan Hubicka
2017-06-08 16:57 ` Jason Merrill
2017-06-09 7:52 ` Jan Hubicka
2017-06-06 16:31 ` Segher Boessenkool
2017-06-06 20:25 ` Jan Hubicka
2017-06-07 18:44 ` Segher Boessenkool
2017-06-07 21:11 ` Jan Hubicka
2017-06-07 21:41 ` Segher Boessenkool
2017-06-05 18:52 Dominique d'Humières
2017-06-05 19:14 ` Jan Hubicka
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=alpine.DEB.2.20.1706051512110.19349@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rep.dot.nop@gmail.com \
/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).