On Wed, 2018-10-31 at 16:14 -0700, Dylan Baker wrote:
> Quoting Jan Vesely (2018-10-31 11:37:19)
> > On Wed, 2018-10-31 at 11:22 -0700, Francisco Jerez wrote:
> > > I don't object removing the pre-LLVM 5.0 paths, nor keeping them around
> > > in order to make r600 happy. What would it take to
Quoting Jan Vesely (2018-10-31 11:37:19)
> On Wed, 2018-10-31 at 11:22 -0700, Francisco Jerez wrote:
> > I don't object removing the pre-LLVM 5.0 paths, nor keeping them around
> > in order to make r600 happy. What would it take to forward-port the
> > r600 image support code to more recent LLVM
On Wed, 2018-10-31 at 11:22 -0700, Francisco Jerez wrote:
> I don't object removing the pre-LLVM 5.0 paths, nor keeping them around
> in order to make r600 happy. What would it take to forward-port the
> r600 image support code to more recent LLVM versions?
Converting the llvm pass to the new
I don't object removing the pre-LLVM 5.0 paths, nor keeping them around
in order to make r600 happy. What would it take to forward-port the
r600 image support code to more recent LLVM versions?
Jan Vesely writes:
> On Wed, 2018-10-31 at 17:02 +, Emil Velikov wrote:
>> On Wed, 31 Oct 2018
On Wed, 2018-10-31 at 17:02 +, Emil Velikov wrote:
> On Wed, 31 Oct 2018 at 15:57, Jan Vesely wrote:
> > On Wed, 2018-10-31 at 13:30 +, Emil Velikov wrote:
> > > From: Emil Velikov
> > >
> > > LLVM versions earlier than 5.0.1 are no longer supported.
> >
> > I'd prefer to keep
On Wed, 31 Oct 2018 at 15:57, Jan Vesely wrote:
>
> On Wed, 2018-10-31 at 13:30 +, Emil Velikov wrote:
> > From: Emil Velikov
> >
> > LLVM versions earlier than 5.0.1 are no longer supported.
>
> I'd prefer to keep llvm-3.9, since it's the last version that supports
> images for r600, but
On Wed, 2018-10-31 at 13:30 +, Emil Velikov wrote:
> From: Emil Velikov
>
> LLVM versions earlier than 5.0.1 are no longer supported.
I'd prefer to keep llvm-3.9, since it's the last version that supports
images for r600, but I'd leave the final decision to Francisco.
Jan
>
> Cc: Jan
