From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72785] bfgminer --scrypt on 7xxx+
Date: Fri, 14 Feb 2014 18:52:05 +0000 [thread overview]
Message-ID: <bug-72785-502-xNFJSkqwM2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72785-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72785
--- Comment #13 from Christoph Haag <haagch.christoph@googlemail.com> ---
Created attachment 94094
--> https://bugs.freedesktop.org/attachment.cgi?id=94094&action=edit
crashing again with patch from #8
(In reply to comment #8)
> Created attachment 94078 [details]
> Patch to test
>
> Can you test this patch and post the output of R600_DEBUG=cs
It's crashing again with
0x7f76ed4687c0: i32 = ExternalSymbol'__muldi3'
For some reason the output seems to be doubled in my log.
I hope it's not a problem that llvm was built from a newer revision than clang.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1847 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
next prev parent reply other threads:[~2014-02-14 18:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 12:19 [Bug 72785] New: bfgminer --scrypt on 7xxx+ bugzilla-daemon
2014-01-03 18:19 ` [Bug 72785] " bugzilla-daemon
2014-01-04 23:52 ` bugzilla-daemon
2014-01-13 17:22 ` bugzilla-daemon
2014-01-13 17:31 ` bugzilla-daemon
2014-02-14 13:59 ` bugzilla-daemon
2014-02-14 14:02 ` bugzilla-daemon
2014-02-14 14:34 ` bugzilla-daemon
2014-02-14 16:18 ` bugzilla-daemon
2014-02-14 16:40 ` bugzilla-daemon
2014-02-14 16:47 ` bugzilla-daemon
2014-02-14 17:43 ` bugzilla-daemon
2014-02-14 17:53 ` bugzilla-daemon
2014-02-14 18:52 ` bugzilla-daemon [this message]
2014-02-14 18:55 ` bugzilla-daemon
2014-02-14 19:28 ` bugzilla-daemon
2014-02-14 19:33 ` bugzilla-daemon
2014-02-14 19:56 ` bugzilla-daemon
2014-02-14 20:12 ` bugzilla-daemon
2014-02-14 20:13 ` bugzilla-daemon
2014-02-14 20:43 ` bugzilla-daemon
2014-02-14 21:07 ` bugzilla-daemon
2014-02-14 21:10 ` bugzilla-daemon
2014-02-14 21:30 ` bugzilla-daemon
2014-02-15 11:52 ` bugzilla-daemon
2014-07-11 22:52 ` bugzilla-daemon
2014-07-14 14:36 ` bugzilla-daemon
2014-07-14 15:18 ` bugzilla-daemon
2014-08-21 16:30 ` bugzilla-daemon
2014-08-21 17:20 ` bugzilla-daemon
2014-08-22 13:49 ` bugzilla-daemon
2014-08-22 13:50 ` bugzilla-daemon
2014-08-23 9:21 ` bugzilla-daemon
2014-11-02 3:08 ` bugzilla-daemon
2014-11-02 12:46 ` bugzilla-daemon
2014-11-22 4:27 ` bugzilla-daemon
2014-11-24 17:43 ` bugzilla-daemon
2014-11-24 18:14 ` bugzilla-daemon
2014-11-24 19:33 ` bugzilla-daemon
2014-11-25 2:46 ` bugzilla-daemon
2014-11-26 17:07 ` bugzilla-daemon
2017-03-22 16:03 ` [Bug 72785] bfgminer --scrypt OpenCL on Clover RadeonSI bugzilla-daemon
2017-03-22 16:03 ` bugzilla-daemon
2018-05-30 6:43 ` 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-72785-502-xNFJSkqwM2@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).