All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97122] list of 12 dEQP-GLES2 tests causing systematic GPU lockups
Date: Mon, 01 Aug 2016 12:08:20 +0000	[thread overview]
Message-ID: <bug-97122-502-bib1VSsFzw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97122-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 448 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=97122

--- Comment #4 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Hi Mauro, thanks for the report - sounds like a control flow lowering bug.

Note that the 'nosb' option will have no effect, it applies to r600 only.

Which version of LLVM are you using? glxinfo shows this. Does the lockup happen
with LLVM trunk?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1249 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

  parent reply	other threads:[~2016-08-01 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 22:54 [Bug 97122] list of 12 dEQP-GLES2 tests causing systematic GPU lockups bugzilla-daemon
2016-07-28 22:57 ` bugzilla-daemon
2016-07-28 23:00 ` bugzilla-daemon
2016-07-28 23:01 ` bugzilla-daemon
2016-08-01 12:08 ` bugzilla-daemon [this message]
2016-08-02  7:24 ` bugzilla-daemon
2016-08-02  7:35 ` bugzilla-daemon
2016-08-02 12:30 ` bugzilla-daemon
2016-08-02 17:41 ` bugzilla-daemon
2016-08-02 21:51 ` 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-97122-502-bib1VSsFzw@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.