From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105333] [gallium-nine] missing geometry after commit ac: replace ac_build_kill with ac_build_kill_if_false
Date: Tue, 10 Apr 2018 07:41:03 +0000 [thread overview]
Message-ID: <bug-105333-502-YXFsAdAiCT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105333-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1178 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105333
iive@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |bisected, regression
--- Comment #3 from iive@yahoo.com ---
Would you make and upload an apitrace of the game demonstrating the issue?
There is an ftp for traces of Gallium Nine, you can ask in Freenode #d3d9
channel for the password, or simply use google drive or other better file
sharing.
The trace might be kept for future regression testing. (Unless you explicitly
oppose.)
It would be nice if you also open issue at github ixit.Mesa-3D, where most of
Gallium Nine bugs are tracked.
Since the bug itself is outside of Nine, it is good that you have it filled
here.
BTW, since the bug is regression and you've located it, be sure to put the
regression and bisected tags/keywords. I just added them. It help developers if
they know that the mundane and time consuming work has already been done. (I
hope.)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2596 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-10 7:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 14:05 [Bug 105333] [gallium-nine] missing geometry after commit ac: replace ac_build_kill with ac_build_kill_if_false bugzilla-daemon
2018-03-03 14:06 ` bugzilla-daemon
2018-03-03 14:07 ` bugzilla-daemon
2018-04-10 7:41 ` bugzilla-daemon [this message]
2018-04-10 15:43 ` bugzilla-daemon
2018-04-21 11:13 ` bugzilla-daemon
2018-08-31 9:35 ` bugzilla-daemon
2018-09-09 12:19 ` bugzilla-daemon
2018-09-09 22:20 ` bugzilla-daemon
2018-09-11 18:01 ` bugzilla-daemon
2018-09-11 18:04 ` bugzilla-daemon
2018-09-13 16:48 ` bugzilla-daemon
2018-09-13 18:24 ` bugzilla-daemon
2018-09-13 18:36 ` bugzilla-daemon
2018-09-13 19:37 ` bugzilla-daemon
2018-09-22 13:10 ` bugzilla-daemon
2018-09-22 14:30 ` bugzilla-daemon
2018-09-22 14:56 ` bugzilla-daemon
2018-09-22 16:56 ` bugzilla-daemon
2018-09-22 17:44 ` bugzilla-daemon
2018-09-22 21:05 ` bugzilla-daemon
2018-09-25 1:36 ` bugzilla-daemon
2018-09-25 7:39 ` bugzilla-daemon
2018-09-26 11:17 ` 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-105333-502-YXFsAdAiCT@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox