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 79649] New: [PATCH RFC] r300/compiler: recursive look for RC_OPCODE_S**
Date: Wed, 04 Jun 2014 19:20:23 +0000	[thread overview]
Message-ID: <bug-79649-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 79649
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [PATCH RFC] r300/compiler: recursive look for
                    RC_OPCODE_S**
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: david.heidelberger@ixit.cz
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r300
           Product: Mesa

Created attachment 100416
  --> https://bugs.freedesktop.org/attachment.cgi?id=100416&action=edit
0001-r300-compiler-recursive-look-for-RC_OPCODE_S.patch

Get rid of error "Failed to build loop info" by fixing failure in cases
like
4:   SGE temp[2].x, temp[0].xxxx, const[0].wwww;
5:   CMP temp[1].x, -temp[2].xxxx, const[0].zzzz, temp[1].xxxx;
6:   IF temp[1].xxxx;

On RS690
 - fixes piglit glean "do-loop with continue and break"
 - changes error from Failed to build loop info ->
   Not a native swizzle: 00000e89
   r300_fragprog_emit.c::begin_tex(): Too many texture indirections
   for "discard statement in for loop"
 - hide Failed to build loop info for
   "precision log2", "while-loop with continue",
   "for-loop with continue" and return "1 1 1 1" insted of "0 0 0 1"

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

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

             reply	other threads:[~2014-06-04 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 19:20 bugzilla-daemon [this message]
2014-06-04 19:24 ` [Bug 79649] [PATCH RFC] r300/compiler: recursive look for RC_OPCODE_S** bugzilla-daemon
2014-06-04 19:26 ` bugzilla-daemon
2014-06-04 19:28 ` bugzilla-daemon
2014-06-04 19:33 ` bugzilla-daemon
2014-06-04 19:34 ` bugzilla-daemon
2014-10-14 12:01 ` 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-79649-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