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 95438] Elemental demo compute shader takes ages to compile
Date: Tue, 17 May 2016 02:01:15 +0000	[thread overview]
Message-ID: <bug-95438-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 95438
           Summary: Elemental demo compute shader takes ages to compile
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: airlied@freedesktop.org
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 123804
  --> https://bugs.freedesktop.org/attachment.cgi?id=123804&action=edit
compute shader and GLSL/TGSI/llvm IR.

After fixing the two GLSL bugs, I hit a case where one of the compute shaders
in 
ElementalDemo takes a long long time to compile and consumes a lot of memory
doing so.


#0  llvm::SUnit::addPred (this=this@entry=0x7fa8da02fae0, D=...,
Required=Required@entry=true)
    at /home/airlied/devel/llvm/lib/CodeGen/ScheduleDAG.cpp:67
#1  0x00007fa92c946d2d in llvm::ScheduleDAGInstrs::addPhysRegDataDeps
(this=this@entry=0x7fa9248d3840, SU=SU@entry=0x7fa8d9833c40, 
    OperIdx=OperIdx@entry=8) at
/home/airlied/devel/llvm/lib/CodeGen/ScheduleDAGInstrs.cpp:318
#2  0x00007fa92c947198 in llvm::ScheduleDAGInstrs::addPhysRegDeps
(this=this@entry=0x7fa9248d3840, SU=SU@entry=0x7fa8d9833c40, 
    OperIdx=OperIdx@entry=8) at
/home/airlied/devel/llvm/lib/CodeGen/ScheduleDAGInstrs.cpp:370
#3  0x00007fa92c94fd1e in llvm::ScheduleDAGInstrs::buildSchedGraph
(this=this@entry=0x7fa9248d3840, AA=0x7fa8e2e55b10, 
    RPTracker=RPTracker@entry=0x0, PDiffs=PDiffs@entry=0x0, LIS=LIS@entry=0x0,
TrackLaneMasks=TrackLaneMasks@entry=false)
    at /home/airlied/devel/llvm/lib/CodeGen/ScheduleDAGInstrs.cpp:959
#4  0x00007fa92c8ff02b in (anonymous namespace)::SchedulePostRATDList::schedule
(this=this@entry=0x7fa9248d3840)
    at /home/airlied/devel/llvm/lib/CodeGen/PostRASchedulerList.cpp:391
#5  0x00007fa92c8ffbbe in (anonymous
namespace)::PostRAScheduler::runOnMachineFunction (this=0x7fa8e284a500, Fn=...)
    at /home/airlied/devel/llvm/lib/CodeGen/PostRASchedulerList.cpp:360
#6  0x00007fa92c880721 in llvm::MachineFunctionPass::runOnFunction
(this=0x7fa8e284a500, F=...)
    at /home/airlied/devel/llvm/lib/CodeGen/MachineFunctionPass.cpp:60

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

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

             reply	other threads:[~2016-05-17  2:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17  2:01 bugzilla-daemon [this message]
2016-05-17  2:30 ` [Bug 95438] Elemental demo compute shader takes ages to compile bugzilla-daemon
2016-05-17  6:13 ` bugzilla-daemon
2016-05-17  6:14 ` bugzilla-daemon
2016-05-24 22:28 ` bugzilla-daemon
2017-01-05 17:52 ` 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-95438-502@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