All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64193] LLVM RV670 regression since R600: Packetize instructions
Date: Tue, 14 May 2013 14:37:26 +0000	[thread overview]
Message-ID: <bug-64193-502-GzOqo1LcUF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64193-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Vadim Girlin <ptpzz@yandex.ru> ---
I looked a bit more into it and AFAICS it's not just a single wrong bit, looks
like r700 alu encoding is used for all r600  chips with llvm backend
currently(In reply to comment #9)
> As mentioned by Vadim on IRC:
> it seems many instructions in bytecode generated for RS880 have (incorrect)
> OMOD = 2, that is, ALU WORD1 bit 7 is set where it shouldn't be set

I looked a bit more into it and AFAICS it's not just a single wrong bit, looks
like r700 alu encoding is used for all r600 chips with llvm backend currently

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

[-- Attachment #1.2: Type: text/html, Size: 1564 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:[~2013-05-14 14:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 18:28 [Bug 64193] New: LLVM RV670 regression since R600: Packetize instructions bugzilla-daemon
2013-05-03 20:15 ` [Bug 64193] " bugzilla-daemon
2013-05-03 22:54 ` bugzilla-daemon
2013-05-03 22:55 ` bugzilla-daemon
2013-05-04 15:51 ` bugzilla-daemon
2013-05-04 18:33 ` bugzilla-daemon
2013-05-04 18:35 ` bugzilla-daemon
2013-05-04 18:36 ` bugzilla-daemon
2013-05-14 14:07 ` bugzilla-daemon
2013-05-14 14:30 ` bugzilla-daemon
2013-05-14 14:37 ` bugzilla-daemon [this message]
2013-05-14 14:42 ` bugzilla-daemon
2013-05-14 14:55 ` bugzilla-daemon
2013-05-14 15:05 ` bugzilla-daemon
2013-05-14 15:05 ` bugzilla-daemon
2013-05-14 15:06 ` bugzilla-daemon
2013-05-14 15:33 ` bugzilla-daemon
2013-05-14 16:07 ` bugzilla-daemon
2013-05-14 17:08 ` bugzilla-daemon
2013-05-14 19:18 ` bugzilla-daemon
2013-05-14 22:20 ` bugzilla-daemon
2013-05-15 11:33 ` bugzilla-daemon
2013-05-15 11:33 ` bugzilla-daemon
2013-05-15 11:34 ` bugzilla-daemon
2013-05-15 16:18 ` bugzilla-daemon
2013-05-15 18:51 ` bugzilla-daemon
2013-05-21  9:10 ` 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-64193-502-GzOqo1LcUF@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.