From: Andrew Pinski <pinskia@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Joseph Myers <joseph@codesourcery.com>,
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Reorgnanization of profile count maintenance code, part 1
Date: Mon, 05 Jun 2017 18:38:00 -0000 [thread overview]
Message-ID: <CA+=Sn1m5mnqsuMcvtW6_zMr4RjtDFR0YwMo8Fj+dXzsSreM7tQ@mail.gmail.com> (raw)
In-Reply-To: <20170605153718.GB84695@kam.mff.cuni.cz>
On Mon, Jun 5, 2017 at 8:37 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
> Hi,
> I have committed the following fix.
I seeing the following error while building aarch64-elf:
/home/jenkins/workspace/BuildToolchainAARCH64_thunder_elf_upstream/toolchain/scripts/../src/gcc/shrink-wrap.c:
In function ‘void handle_simple_exit(edge_def*)’:
/home/jenkins/workspace/BuildToolchainAARCH64_thunder_elf_upstream/toolchain/scripts/../src/gcc/shrink-wrap.c:565:
error: ‘struct edge_def’ has no member named ‘frequency’
Thanks,
Andrew
>
> Honza
>
> Index: ChangeLog
> ===================================================================
> --- ChangeLog (revision 248878)
> +++ ChangeLog (working copy)
> @@ -1,5 +1,10 @@
> 2017-06-05 Jan Hubicka <hubicka@ucw.cz>
>
> + * config/mips/frame-header-opt.c: Include profile-count.h.
> + * config/riscv/riscv.c: Include profile-count.h
> +
> +2017-06-05 Jan Hubicka <hubicka@ucw.cz>
> +
> * tree-ssa-loop-im.c (execute_sm_if_changed): Add FLAG_BBS parameter;
> update profile.
> (sm_set_flag_if_changed): Add bbs field.
> Index: config/mips/frame-header-opt.c
> ===================================================================
> --- config/mips/frame-header-opt.c (revision 248871)
> +++ config/mips/frame-header-opt.c (working copy)
> @@ -32,6 +32,7 @@ along with GCC; see the file COPYING3.
> #include "tree-pass.h"
> #include "target.h"
> #include "target-globals.h"
> +#include "profile-count.h"
> #include "cfg.h"
> #include "cgraph.h"
> #include "function.h"
> Index: config/riscv/riscv.c
> ===================================================================
> --- config/riscv/riscv.c (revision 248871)
> +++ config/riscv/riscv.c (working copy)
> @@ -73,6 +73,7 @@ along with GCC; see the file COPYING3.
> #include "common/common-target.h"
> #include "langhooks.h"
> #include "dominance.h"
> +#include "profile-count.h"
> #include "cfg.h"
> #include "cfgrtl.h"
> #include "cfganal.h"
next prev parent reply other threads:[~2017-06-05 18:38 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
2017-06-05 15:16 ` Jan Hubicka
2017-06-05 15:37 ` Jan Hubicka
2017-06-05 18:38 ` Andrew Pinski [this message]
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='CA+=Sn1m5mnqsuMcvtW6_zMr4RjtDFR0YwMo8Fj+dXzsSreM7tQ@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=joseph@codesourcery.com \
--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).