From: Steve Ellcey <sellcey@mips.com>
To: Teresa Johnson <tejohnson@google.com>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
Sebastian Pop <sebpop@gmail.com>, Jeff Law <law@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>, David Li <davidxl@google.com>
Subject: Re: [PATCH] Redesign jump threading profile updates
Date: Wed, 01 Oct 2014 22:46:00 -0000 [thread overview]
Message-ID: <1412203567.2740.488.camel@ubuntu-sellcey> (raw)
In-Reply-To: <CAAe5K+XWZEJPkhnM_2TFmh0VN9u_qXpVGfddUZ71YZkD8kMfXg@mail.gmail.com>
On Wed, 2014-10-01 at 13:04 -0700, Teresa Johnson wrote:
> 2014-10-01 Teresa Johnson <tejohnson@google.com>
>
> * tree-ssa-threadupdate.c (freqs_to_counts_path): Scale frequencies
> up when synthesizing counts to avoid rounding errors.
I tried this patch on my MIPS toolchain build but GCC is still failing
while building glibc.
iconv_open.c: In function 'iconv_open':
iconv_open.c:32:1: error: verify_flow_info: Wrong probability of edge
14->18 -920374544
iconv_open (const char *tocode, const char *fromcode)
^
iconv_open.c:32:1: error: verify_flow_info: Wrong probability of edge
14->19 -903724544
iconv_open.c:32:1: internal compiler error: verify_flow_info failed
0x626a70 verify_flow_info()
/scratch/sellcey/repos/nightly/src/gcc/gcc/cfghooks.c:260
0x9f36e4 cleanup_tree_cfg_noloop
/scratch/sellcey/repos/nightly/src/gcc/gcc/tree-cfgcleanup.c:765
0x9f36e4 cleanup_tree_cfg()
/scratch/sellcey/repos/nightly/src/gcc/gcc/tree-cfgcleanup.c:814
0x8eeff4 execute_function_todo
/scratch/sellcey/repos/nightly/src/gcc/gcc/passes.c:1704
0x8efb23 execute_todo
/scratch/sellcey/repos/nightly/src/gcc/gcc/passes.c:1808
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2014-10-01 22:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 23:57 Teresa Johnson
2014-04-17 5:58 ` Jeff Law
2014-04-17 13:46 ` Teresa Johnson
2014-05-27 14:11 ` Teresa Johnson
2014-07-07 21:22 ` Teresa Johnson
2014-07-07 21:24 ` Jeff Law
2014-07-23 13:47 ` Jeff Law
2014-07-23 21:52 ` Teresa Johnson
2014-08-02 5:10 ` Teresa Johnson
2014-08-02 5:16 ` Andrew Pinski
2014-09-29 14:20 ` Teresa Johnson
2014-09-30 4:33 ` Jeff Law
2014-09-30 18:20 ` Teresa Johnson
2014-10-01 7:03 ` Christophe Lyon
2014-10-01 13:21 ` Teresa Johnson
2014-10-01 14:05 ` Teresa Johnson
2014-10-01 15:23 ` Sebastian Pop
2014-10-01 15:25 ` Christophe Lyon
2014-10-01 15:29 ` Teresa Johnson
2014-10-01 16:20 ` H.J. Lu
2014-10-01 16:23 ` Teresa Johnson
2014-10-01 20:05 ` Teresa Johnson
2014-10-01 22:46 ` Steve Ellcey [this message]
2014-10-02 5:02 ` Teresa Johnson
2014-10-02 15:44 ` Teresa Johnson
2014-10-02 15:45 ` Steve Ellcey
2014-10-02 16:01 ` Teresa Johnson
2014-10-01 23:09 ` Jan Hubicka
2014-10-02 5:07 ` Teresa Johnson
2014-10-02 18:34 ` Jeff Law
2014-10-28 16:01 ` Renlin Li
2014-10-01 15:36 ` Sebastian Pop
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=1412203567.2740.488.camel@ubuntu-sellcey \
--to=sellcey@mips.com \
--cc=christophe.lyon@linaro.org \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=sebpop@gmail.com \
--cc=tejohnson@google.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).