All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97003] [d3dadapter+radeonsi] Dragon's Dogma: video memory leak with precompiled shaders
Date: Fri, 22 Jul 2016 09:16:34 +0000	[thread overview]
Message-ID: <bug-97003-502-niBC2ixrlq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97003-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Michel Dänzer <michel@daenzer.net> ---
(In reply to kudahkukarek from comment #5)
> I rebuilt wine with -march=amdfam10 and still get the same error [...]

The instruction valgrind doesn't know could be in Mesa or any other library
used by Wine.


> [...] I use an Intel CPU and 32-bit wine.

It's probably an instruction from a recent Intel extension then.

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

[-- Attachment #1.2: Type: text/html, Size: 1467 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-07-22  9:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20  8:33 [Bug 97003] [d3dadapter+radeonsi] Dragon's Dogma: video memory leak with precompiled shaders bugzilla-daemon
2016-07-20  8:38 ` bugzilla-daemon
2016-07-20 23:35 ` bugzilla-daemon
2016-07-21  2:07 ` bugzilla-daemon
2016-07-21  4:10 ` bugzilla-daemon
2016-07-22  9:08 ` bugzilla-daemon
2016-07-22  9:16 ` bugzilla-daemon [this message]
2016-07-23  1:07 ` bugzilla-daemon
2017-02-14  2:53 ` bugzilla-daemon
2018-08-31  6:30 ` 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-97003-502-niBC2ixrlq@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.