From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28517] [r300g] loop unrolling fails (was: Savage 2 : characters are not rendered + another corruptions)
Date: Mon, 30 Aug 2010 12:01:04 -0700 (PDT) [thread overview]
Message-ID: <20100830190104.B87EA13007B@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28517-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #30 from Pavel Ondračka <drakkk@centrum.cz> 2010-08-30 12:01:04 PDT ---
(In reply to comment #29)
> Created an attachment (id=38306)
View: https://bugs.freedesktop.org/attachment.cgi?id=38306
Review: https://bugs.freedesktop.org/review?bug=28517&attachment=38306
> Reduce the number of loop iterations
>
> Does this patch impact performance at all?
No noticeable difference with you patch. BTW I did repeat bisecting and it
again showed commit c298bab60ea63882f34825a35cbc60f662783e64 as the one
introducing this slowness. So indeed your analysis in comment 17 looks right. I
wasn't able to bisect any further slowdown with glsl2 merge which Sven
mentioned in comment 24. However we might have different setups because for
example I don't have any troubles with libtxc_dxtn.so
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2010-08-30 19:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 9:58 [Bug 28517] New: [r300g] Savage 2 : characters are not rendered + another corruptions bugzilla-daemon
2010-06-13 9:59 ` [Bug 28517] " bugzilla-daemon
2010-06-13 9:59 ` bugzilla-daemon
2010-06-13 11:18 ` bugzilla-daemon
2010-06-24 8:38 ` bugzilla-daemon
2010-06-26 19:27 ` bugzilla-daemon
2010-06-26 20:25 ` bugzilla-daemon
2010-06-26 21:12 ` bugzilla-daemon
2010-07-08 19:45 ` [Bug 28517] [r300g] loop unrolling fails (was: Savage 2 : characters are not rendered + another corruptions) bugzilla-daemon
2010-08-06 6:37 ` bugzilla-daemon
2010-08-06 10:33 ` bugzilla-daemon
2010-08-06 18:27 ` bugzilla-daemon
2010-08-06 18:42 ` bugzilla-daemon
2010-08-10 5:48 ` bugzilla-daemon
2010-08-10 8:33 ` bugzilla-daemon
2010-08-10 14:51 ` bugzilla-daemon
2010-08-19 14:39 ` bugzilla-daemon
2010-08-25 8:49 ` bugzilla-daemon
2010-08-25 13:46 ` bugzilla-daemon
2010-08-25 14:20 ` bugzilla-daemon
2010-08-25 14:32 ` bugzilla-daemon
2010-08-25 15:09 ` bugzilla-daemon
2010-08-25 20:55 ` bugzilla-daemon
2010-08-26 1:20 ` bugzilla-daemon
2010-08-26 13:38 ` bugzilla-daemon
2010-08-26 21:09 ` bugzilla-daemon
2010-08-26 21:32 ` bugzilla-daemon
2010-08-26 22:41 ` bugzilla-daemon
2010-08-26 23:09 ` bugzilla-daemon
2010-08-26 23:31 ` bugzilla-daemon
2010-08-27 7:37 ` bugzilla-daemon
2010-08-30 16:08 ` bugzilla-daemon
2010-08-30 19:01 ` bugzilla-daemon [this message]
2010-08-30 19:24 ` bugzilla-daemon
2010-09-01 21:21 ` bugzilla-daemon
2010-09-03 19:19 ` bugzilla-daemon
2010-09-03 20:48 ` bugzilla-daemon
2010-09-04 6:14 ` bugzilla-daemon
2010-09-04 9:49 ` bugzilla-daemon
2010-09-04 12:12 ` bugzilla-daemon
2010-09-04 12:59 ` bugzilla-daemon
2010-09-05 20:02 ` bugzilla-daemon
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=20100830190104.B87EA13007B@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.