From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92900] [regression bisected] About 700 piglit regressions is what could go wrong
Date: Wed, 11 Nov 2015 08:46:26 +0000 [thread overview]
Message-ID: <bug-92900-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1911 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92900
Bug ID: 92900
Summary: [regression bisected] About 700 piglit regressions is
what could go wrong
Product: Mesa
Version: 11.0
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R100
Assignee: dri-devel@lists.freedesktop.org
Reporter: idr@freedesktop.org
QA Contact: dri-devel@lists.freedesktop.org
About 700 piglit tests regressed on r100. This includes, but is not limited
to:
All 648 subcases of clipflat
fbo-1d
fbo-clearmipmap
fbo-sys-sub-blit
gen-nonzero-unit
...
At least fbo-clearmipmap bisected to the following commit. I did this bisect
using 'git bisect run' with that one test, and I haven't verified all the
others yet.
Tested on:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV200
[Radeon 7500/7500 LE]
This commit is in Mesa 11.0.
d21320f6258b2e1780a15c1ca718963d8a15ca18 is the first bad commit
commit d21320f6258b2e1780a15c1ca718963d8a15ca18
Author: Roland Scheidegger <sroland@vmware.com>
Date: Thu Jul 16 03:18:20 2015 +0200
radeon: fix some potential big endian issues
The formats chosen (both by texture format choser, fbo storage allocation)
are different for big endian not just for rgba8 but also lower bit width
formats (why I don't actually know). Even the function to test for
renderable
formats used different formats, however the actual colorbuffer setup did
not.
And the blitter did not take that into account neither.
Untested (what could possibly go wrong...).
Acked-by: Marek Olšák <marek.olsak@amd.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3401 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-11-11 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 8:46 bugzilla-daemon [this message]
2015-11-11 14:35 ` [Bug 92900] [regression bisected] About 700 piglit regressions is what could go wrong bugzilla-daemon
2015-11-11 17:25 ` bugzilla-daemon
2015-11-11 17:53 ` bugzilla-daemon
2015-11-12 0:07 ` bugzilla-daemon
2015-11-12 19:02 ` bugzilla-daemon
2015-11-17 0:12 ` bugzilla-daemon
2015-11-17 16:15 ` 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=bug-92900-502@http.bugs.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.