From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90523] Easily reproducible GPU lockup (verde) with any mesa 10.5.x
Date: Thu, 21 May 2015 02:23:02 +0000 [thread overview]
Message-ID: <bug-90523-502-FRU7m7Py8O@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90523-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1465 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90523
--- Comment #7 from Michel Dänzer <michel@daenzer.net> ---
(In reply to acab from comment #6)
> Yes I could, however upsteam appears to maintain llvm in svn.
> There is a git repository as well but it lacks branches and tags.
The Git repository at http://llvm.org/git/llvm.git does have the release
branches. Also, the SVN revision number is included in the Git commit log, so
it's easy to find the Git commit corresponding to a given SVN revision e.g. in
gitk.
> r214336 | rafael.espindola | 2014-07-30 17:04:00 -0400 (Wed, 30 Jul 2014) |
> 9 lines
>
> SimplifyCFG: Avoid miscompilations due to removed lifetime intrinsics.
>
> Which appears to match commit 7fef5a3d1907c813712fcb2a44d8187a65ba08cd:
> [...]
> However mesa 10.5.5 doesn't build against that llvm (doesn't like
> TM->getSubtargetImpl()->getInstrInfo() in lp_bld_debug.cpp), but it does
> build against 3.5.2.
7fef5a3d1907c813712fcb2a44d8187a65ba08cd is on the master branch. The
corresponding commit on the release_35 branch is
a4cf325e41fca33c7ce7deef39a7bcf25fb38266.
However, as I mentioned before, you most likely will run into more similar
issues during the bisection, because Mesa can only test for minor versions of
LLVM, not for individual revisions. You may need to tweak the Mesa code to make
it build in some cases.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2451 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:[~2015-05-21 2:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 19:12 [Bug 90523] Easily reproducible GPU lockup (verde) with any mesa 10.5.x bugzilla-daemon
2015-05-19 19:13 ` bugzilla-daemon
2015-05-19 19:20 ` bugzilla-daemon
2015-05-19 19:56 ` bugzilla-daemon
2015-05-19 19:58 ` bugzilla-daemon
2015-05-19 19:59 ` bugzilla-daemon
2015-05-20 1:14 ` bugzilla-daemon
2015-05-20 1:15 ` bugzilla-daemon
2015-05-20 1:17 ` bugzilla-daemon
2015-05-20 13:51 ` bugzilla-daemon
2015-05-21 2:23 ` bugzilla-daemon [this message]
2015-05-22 20:33 ` bugzilla-daemon
2015-05-22 21:41 ` 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-90523-502-FRU7m7Py8O@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