public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/48283] gcc.dg/graphite/block-[3478].c timeouts
Date: Sun, 14 Jul 2013 05:33:00 -0000 [thread overview]
Message-ID: <bug-48283-4-eFvcsCZDVj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48283-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48283
Sebastian Pop <spop at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Sebastian Pop <spop at gcc dot gnu.org> ---
Works much faster on trunk than what comment#1 reported:
on my ARM laptop exynos5 at 1.6GHz
block-3.c
Graphite loop transforms: 1.61 (71%) usr 0.01 ( 7%) sys 1.68 (57%) wall
61 kB ( 2%) ggc
Graphite data dep analysis: 0.05 ( 2%) usr 0.00 ( 0%) sys 0.05 ( 2%)
wall 0 kB ( 0%) ggc
Graphite code generation: 0.11 ( 5%) usr 0.00 ( 0%) sys 0.11 ( 4%) wall
33 kB ( 1%) ggc
block-4.c
Graphite loop transforms: 1.43 (74%) usr 0.03 (50%) sys 1.82 (78%) wall
39 kB ( 2%) ggc
Graphite data dep analysis: 0.38 (20%) usr 0.00 ( 0%) sys 0.35 (15%)
wall 0 kB ( 0%) ggc
block-5.c
Graphite loop transforms: 0.52 (67%) usr 0.00 ( 0%) sys 0.51 (61%) wall
30 kB ( 1%) ggc
Graphite data dep analysis: 0.02 ( 3%) usr 0.00 ( 0%) sys 0.02 ( 2%)
wall 0 kB ( 0%) ggc
Graphite code generation: 0.02 ( 3%) usr 0.00 ( 0%) sys 0.03 ( 4%) wall
17 kB ( 1%) ggc
block-6.c
Graphite loop transforms: 0.22 (67%) usr 0.00 ( 0%) sys 0.21 (55%) wall
19 kB ( 1%) ggc
block-7.c
Graphite loop transforms: 2.34 (75%) usr 0.01 (11%) sys 2.41 (72%) wall
49 kB ( 2%) ggc
Graphite data dep analysis: 0.43 (14%) usr 0.01 (11%) sys 0.46 (14%)
wall 0 kB ( 0%) ggc
Graphite code generation: 0.14 ( 4%) usr 0.01 (11%) sys 0.15 ( 5%) wall
45 kB ( 2%) ggc
block-8.c
Graphite loop transforms: 2.34 (73%) usr 0.01 (17%) sys 2.37 (72%) wall
59 kB ( 2%) ggc
Graphite data dep analysis: 0.42 (13%) usr 0.00 ( 0%) sys 0.42 (13%)
wall 0 kB ( 0%) ggc
Graphite code generation: 0.13 ( 4%) usr 0.01 (17%) sys 0.13 ( 4%) wall
45 kB ( 2%) ggc
prev parent reply other threads:[~2013-07-14 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 11:47 [Bug testsuite/48283] New: " ro at gcc dot gnu.org
2011-03-25 13:00 ` [Bug testsuite/48283] " rguenth at gcc dot gnu.org
2011-03-25 13:02 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-03-25 14:06 ` ro at gcc dot gnu.org
2011-05-18 0:01 ` michael.hope at linaro dot org
2013-07-14 5:33 ` spop at gcc dot gnu.org [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=bug-48283-4-eFvcsCZDVj@http.gcc.gnu.org/bugzilla/ \
--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).