All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66730] New: [LLVM radeonsi] Infinite loop in LLVM backend possible when using "double" arguments
Date: Tue, 09 Jul 2013 10:46:22 +0000	[thread overview]
Message-ID: <bug-66730-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 66730
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [LLVM radeonsi] Infinite loop in LLVM backend possible
                    when using "double" arguments
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: niels_ole@salscheider-online.de
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 82223
  --> https://bugs.freedesktop.org/attachment.cgi?id=82223&action=edit
testcase

Some expressions containing multiple double precision kernel arguments cause
llvm to run until all memory is used. It works fine as long as I pass pointers
to double values.

I have attached an LLVM IR testcase that triggers the described behaviour.

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

[-- Attachment #1.2: Type: text/html, Size: 2442 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:[~2013-07-09 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 10:46 bugzilla-daemon [this message]
2013-11-16  2:34 ` [Bug 66730] [LLVM radeonsi] Infinite loop in LLVM backend possible when using "double" arguments bugzilla-daemon
2013-11-16  2:34 ` 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-66730-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 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.