dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89034] Firefox crashing xserver and some major rendering bugs
Date: Sat, 21 Feb 2015 08:42:34 +0000	[thread overview]
Message-ID: <bug-89034-502-PaZu7tKawp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89034-502@http.bugs.freedesktop.org/>


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

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

--- Comment #23 from smoki <smoki00790@gmail.com> ---
Created attachment 113715
  --> https://bugs.freedesktop.org/attachment.cgi?id=113715&action=edit
valley.png

(In reply to Tom Stellard from comment #22)
> Created attachment 113709 [details] [review]
> Patch to re-enable subreg liveness
> 
> I think this bug has been fixed.  This patch re-enables subreg livess.  Can
> you see if the issue still exists with this patch applied to LLVM git.

 Just tried it on top of svn230129... Firefox does not crash xserver anymore,
but rendering is still broken mostly fine now in valley, that "half picture"
broken rendering is also fixed
https://bugs.freedesktop.org/attachment.cgi?id=113269... but there are still
black squares appear here and there - see attachment. Basically firefox xserver
crash is fixed, but rendering in games is not... and i have some other examples
when rendering is much worse.

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

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

  parent reply	other threads:[~2015-02-21  8:42 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09  6:08 [Bug 89034] Firefox crashing xserver and some major rendering bugs bugzilla-daemon
2015-02-09  6:10 ` bugzilla-daemon
2015-02-09  6:22 ` bugzilla-daemon
2015-02-09  6:40 ` bugzilla-daemon
2015-02-09  6:52 ` bugzilla-daemon
2015-02-09  7:56 ` bugzilla-daemon
2015-02-09  8:04 ` bugzilla-daemon
2015-02-09  8:40 ` bugzilla-daemon
2015-02-09  8:54 ` bugzilla-daemon
2015-02-09  9:33 ` bugzilla-daemon
2015-02-10  1:29 ` bugzilla-daemon
2015-02-10 10:22 ` bugzilla-daemon
2015-02-10 10:23 ` bugzilla-daemon
2015-02-10 10:30 ` bugzilla-daemon
2015-02-11  4:41 ` bugzilla-daemon
2015-02-11 10:21 ` bugzilla-daemon
2015-02-11 10:22 ` bugzilla-daemon
2015-02-11 10:22 ` bugzilla-daemon
2015-02-11 10:26 ` bugzilla-daemon
2015-02-11 18:28 ` bugzilla-daemon
2015-02-12  8:12 ` bugzilla-daemon
2015-02-12  8:50 ` bugzilla-daemon
2015-02-12 16:01 ` bugzilla-daemon
2015-02-21  0:33 ` bugzilla-daemon
2015-02-21  8:42 ` bugzilla-daemon [this message]
2015-02-21  8:49 ` bugzilla-daemon
2015-02-21  9:08 ` bugzilla-daemon
2015-02-21  9:15 ` bugzilla-daemon
2015-02-21 13:38 ` bugzilla-daemon
2015-02-23 18:41 ` bugzilla-daemon
2015-02-23 23:13 ` bugzilla-daemon
2015-02-24  6:59 ` bugzilla-daemon
2015-02-24 13:14 ` bugzilla-daemon
2015-02-24 20:20 ` bugzilla-daemon
2015-02-24 21:13 ` bugzilla-daemon
2015-02-25  9:02 ` bugzilla-daemon
2015-02-25  9:51 ` bugzilla-daemon
2015-02-25  9:52 ` bugzilla-daemon
2015-02-25 17:01 ` bugzilla-daemon
2015-02-25 17:52 ` bugzilla-daemon
2015-02-25 18:12 ` bugzilla-daemon
2015-03-20  0:33 ` bugzilla-daemon
2015-03-20 21:10 ` bugzilla-daemon
2015-03-23 17:27 ` bugzilla-daemon
2015-03-23 21:13 ` bugzilla-daemon
2015-03-24 13:49 ` bugzilla-daemon
2015-03-24 15:12 ` bugzilla-daemon
2015-03-24 21:17 ` bugzilla-daemon
2015-03-28  1:06 ` bugzilla-daemon
2015-03-28  6:18 ` bugzilla-daemon
2015-05-26  0:55 ` 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-89034-502-PaZu7tKawp@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