dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56437] New: LLVM ERROR: Cannot select: target intrinsic %llvm.AMDIL.mad when running Heaven
Date: Fri, 26 Oct 2012 17:44:36 +0000	[thread overview]
Message-ID: <bug-56437-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 56437
          Assignee: dri-devel@lists.freedesktop.org
           Summary: LLVM ERROR: Cannot select: target intrinsic
                    %llvm.AMDIL.mad when running Heaven
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: maxijac@free.fr
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Drivers/Gallium/r600
           Product: Mesa

Heaven sometimes crashes when loading with an error output :
LLVM ERROR: Cannot select: target intrinsic %llvm.AMDIL.mad

I can partially reproduce this bug.
It happens from time to time on Heaven start.

To reproduce it I use the Heaven launcher (using Archlinux AUR package), just
untick fullscreen checkbox and choose 1024x768 and click run.
If the crash is not triggered I close the unigine render window and just click
once again "Run" and so on.

It happens about once every 10 runs when I test. (I know it's not convenient at
all to reproduce it but it is a very rare bug...) I also had it once with
Heroes of Newerth.

using R600_LLVM=0, radeon seems to be not hit by this problem.

Using git head and r600g on BARTS HD6870.

I might also add that I use these env vars (some are probably outdated...)
R600_ENABLE_S3TC=1
R600_GLSL130=1
R600_STREAMOUT=1

Using Xorg 1.13 and linux 3.6.3

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

[-- Attachment #1.2: Type: text/html, Size: 2840 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:[~2012-10-26 17:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 17:44 bugzilla-daemon [this message]
2012-10-26 17:44 ` [Bug 56437] LLVM ERROR: Cannot select: target intrinsic %llvm.AMDIL.mad when running Heaven bugzilla-daemon
2012-10-26 18:13 ` bugzilla-daemon
2012-10-26 22:57 ` bugzilla-daemon
2012-10-29 17:18 ` bugzilla-daemon
2012-10-29 20:13 ` bugzilla-daemon
2012-10-29 22:23 ` bugzilla-daemon
2012-10-30 10:30 ` bugzilla-daemon
2012-10-30 13:43 ` bugzilla-daemon
2012-10-30 16:05 ` bugzilla-daemon
2012-10-30 19:44 ` bugzilla-daemon
2012-10-30 19:45 ` bugzilla-daemon
2012-10-30 19:47 ` bugzilla-daemon
2012-10-30 20:51 ` bugzilla-daemon
2012-10-31 15:27 ` bugzilla-daemon
2012-10-31 17:26 ` bugzilla-daemon
2013-04-05 20:46 ` 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-56437-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;
as well as URLs for NNTP newsgroup(s).