Comment # 6
on bug 90523
from acab@digitalfuture.it
(In reply to Michel Dänzer from comment #5) > Can you try isolating the LLVM change introducing it with git bisect? Note > that this might require some tweaking because current Mesa might fail to > build against some development snapshots of LLVM. Yes I could, however upsteam appears to maintain llvm in svn. There is a git repository as well but it lacks branches and tags. Additionally the branch history doesn't look very linear and so far i've failed to match the proper commit from the branch in master. For example the top commit in http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_352/final is: ------------------------------------------------------------------------ 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: Author: Rafael Espindola <rafael.espindola@gmail.com> Date: Wed Jul 30 21:04:00 2014 +0000 SimplifyCFG: Avoid miscompilations due to removed lifetime intrinsics. 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. Can you suggest some commit ids i could use as good and bad markers?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
