From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 34495] Selecting objects in Blender 2.56 slow with gallium r600
driver
Date: Tue, 28 Jun 2011 06:53:45 -0700 (PDT)
Message-ID: <20110628135346.1ADD513004D@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 643079E79D
for ;
Tue, 28 Jun 2011 06:53:47 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=34495
--- Comment #18 from Micael Dias 2011-06-28 06:53:45 PDT ---
@Sergei: no problem. This bug was also hitting on my nerves for months, and I
was always curious about how the linux graphics stack actually works, so I
decided to see if I could see where this bug was comming from.
After having llvm generate some printfs it was pretty obvious that the issue
was some kind of buffer overflow. Then generating hardcoded values on
generate_fetch() and not having the crash anymore was a key clue that that was
corrupting the memory somehow. Funny enough draw_llvm_generate_elts() checks
for these buffer overflows, so it was almost copy-paste from there. I'm not
even sure this is a proper fix since draw_llvm_generate_elts does a little more
than I do here.
@Pierre: It's a pitty if it doesn get hardware accelerated. Many CAD apps use
GL_SELECT. Can you please give me a hint on how one would go about implementing
HW acceleration for it? I'm not sure I'm able to do it, but would be interested
in playing with it.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.