Comment=
# 7
on bug 90523<=
/a>
from Michel D=C3=A4nzer
(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
>=20
> SimplifyCFG: Avoid miscompilations due to removed lifetime intrinsics.
>=20
> 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.