I don't see the code question, but I do see uses of the "inline" keyword in
ImageMagick. C99 inline does not mean what everyone seems to think it means,
and is not really a demand or even request to inline the function.
For example at -O1 on x86, this gives:
inline void bar(global int* arg) {
On Sat, Jun 1, 2019 at 11:24 PM Marek Olšák wrote:
>
> clover is not supported by AMD officially, because AMD has its own OpenCL
> driver called ROCm.
>
> Marek
ROCm isn't a viable option for many. Official support only goes back
to Fiji . Running without PCIe atomics support only applies to V
On Mon, 3 Jun 2019 at 11:37, Jan Vesely wrote:
>
> On Mon, 2019-06-03 at 11:12 +1000, Dave Airlie wrote:
> > On Mon, 3 Jun 2019 at 10:58, Jan Vesely wrote:
> > > On Sun, 2019-06-02 at 20:09 -0400, James Harvey wrote:
> > > > I've started a thread on the llvm mailing list. See
> > > > https://nam
On Mon, 2019-06-03 at 11:12 +1000, Dave Airlie wrote:
> On Mon, 3 Jun 2019 at 10:58, Jan Vesely wrote:
> > On Sun, 2019-06-02 at 20:09 -0400, James Harvey wrote:
> > > I've started a thread on the llvm mailing list. See
> > > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.
On Mon, 3 Jun 2019 at 10:42, Jan Vesely wrote:
>
> On Mon, 2019-06-03 at 09:14 +1000, Dave Airlie wrote:
> > On Mon, 3 Jun 2019 at 09:13, Dave Airlie wrote:
> > > On Sun, 2 Jun 2019 at 23:13, Jan Vesely wrote:
> > > > On Sun, 2019-06-02 at 07:17 -0400, James Harvey wrote:
> > > > > On Sun, Jun 2
On Mon, 3 Jun 2019 at 10:58, Jan Vesely wrote:
>
> On Sun, 2019-06-02 at 20:09 -0400, James Harvey wrote:
> > I've started a thread on the llvm mailing list. See
> > http://lists.llvm.org/pipermail/llvm-dev/2019-June/132750.html
> >
> > I don't know if it's needed, but if anyone has a commit in l
On Sun, 2019-06-02 at 20:09 -0400, James Harvey wrote:
> I've started a thread on the llvm mailing list. See
> http://lists.llvm.org/pipermail/llvm-dev/2019-June/132750.html
>
> I don't know if it's needed, but if anyone has a commit in llvm that
> started this, that might be helpful.
thanks. ho
On Mon, 2019-06-03 at 09:14 +1000, Dave Airlie wrote:
> On Mon, 3 Jun 2019 at 09:13, Dave Airlie wrote:
> > On Sun, 2 Jun 2019 at 23:13, Jan Vesely wrote:
> > > On Sun, 2019-06-02 at 07:17 -0400, James Harvey wrote:
> > > > On Sun, Jun 2, 2019 at 7:01 AM Bas Nieuwenhuizen
> > > > wrote:
> > > >
I've started a thread on the llvm mailing list. See
http://lists.llvm.org/pipermail/llvm-dev/2019-June/132750.html
I don't know if it's needed, but if anyone has a commit in llvm that
started this, that might be helpful.
On Sat, Jun 1, 2019 at 10:56 PM Jan Vesely wrote:
>
> Hi,
>
> On Sat, 2019
On Mon, 3 Jun 2019 at 09:13, Dave Airlie wrote:
>
> On Sun, 2 Jun 2019 at 23:13, Jan Vesely wrote:
> >
> > On Sun, 2019-06-02 at 07:17 -0400, James Harvey wrote:
> > > On Sun, Jun 2, 2019 at 7:01 AM Bas Nieuwenhuizen
> > > wrote:
> > > > On Sun, Jun 2, 2019 at 12:41 PM James Harvey
> > > > wro
On Sun, 2 Jun 2019 at 23:13, Jan Vesely wrote:
>
> On Sun, 2019-06-02 at 07:17 -0400, James Harvey wrote:
> > On Sun, Jun 2, 2019 at 7:01 AM Bas Nieuwenhuizen
> > wrote:
> > > On Sun, Jun 2, 2019 at 12:41 PM James Harvey
> > > wrote:
> > > > So, for people running amdgpu and wanting to run Imag
On Sun, 2019-06-02 at 07:17 -0400, James Harvey wrote:
> On Sun, Jun 2, 2019 at 7:01 AM Bas Nieuwenhuizen
> wrote:
> > On Sun, Jun 2, 2019 at 12:41 PM James Harvey
> > wrote:
> > > So, for people running amdgpu and wanting to run ImageMagick convert
> > > who get this error... Does this mean the
On Sun, Jun 2, 2019 at 7:01 AM Bas Nieuwenhuizen
wrote:
> On Sun, Jun 2, 2019 at 12:41 PM James Harvey wrote:
> > So, for people running amdgpu and wanting to run ImageMagick convert
> > who get this error... Does this mean there is something ImageMagick
> > could change to prevent the error? Or
On Sun, Jun 2, 2019 at 12:41 PM James Harvey wrote:
>
> On Sat, Jun 1, 2019 at 10:56 PM Jan Vesely wrote:
> > On Sat, 2019-06-01 at 18:21 -0400, James Harvey wrote:
> > > On Sat, Jun 1, 2019 at 6:19 PM James Harvey
> > > wrote:
> > > > On Tue, Feb 19, 2019 at 7:52 PM james harvey
> > > > wrot
On Sat, Jun 1, 2019 at 10:56 PM Jan Vesely wrote:
> On Sat, 2019-06-01 at 18:21 -0400, James Harvey wrote:
> > On Sat, Jun 1, 2019 at 6:19 PM James Harvey
> > wrote:
> > > On Tue, Feb 19, 2019 at 7:52 PM james harvey
> > > wrote:
> > > > Commit 9baacf3f is: "radeonsi: Refuse to accept code wit
clover is not supported by AMD officially, because AMD has its own OpenCL
driver called ROCm.
Marek
On Sat, Jun 1, 2019, 10:56 PM Jan Vesely wrote:
> Hi,
>
> On Sat, 2019-06-01 at 18:21 -0400, James Harvey wrote:
> > On Sat, Jun 1, 2019 at 6:19 PM James Harvey
> wrote:
> > > On Tue, Feb 19, 2
Hi,
On Sat, 2019-06-01 at 18:21 -0400, James Harvey wrote:
> On Sat, Jun 1, 2019 at 6:19 PM James Harvey wrote:
> > On Tue, Feb 19, 2019 at 7:52 PM james harvey
> > wrote:
> > > Commit 9baacf3f is: "radeonsi: Refuse to accept code with unhandled
> > > relocations".
> > >
> > > This has broken
On Sat, Jun 1, 2019 at 6:19 PM James Harvey wrote:
>
> On Tue, Feb 19, 2019 at 7:52 PM james harvey wrote:
> >
> > Commit 9baacf3f is: "radeonsi: Refuse to accept code with unhandled
> > relocations".
> >
> > This has broken ImageMagick for many people using AMD graphics cards.
> > See https://gi
On Tue, Feb 19, 2019 at 7:52 PM james harvey wrote:
>
> Commit 9baacf3f is: "radeonsi: Refuse to accept code with unhandled
> relocations".
>
> This has broken ImageMagick for many people using AMD graphics cards.
> See https://github.com/ImageMagick/ImageMagick/issues/1366
>
> ImageMagick respond
Commit 9baacf3f is: "radeonsi: Refuse to accept code with unhandled
relocations".
This has broken ImageMagick for many people using AMD graphics cards.
See https://github.com/ImageMagick/ImageMagick/issues/1366
ImageMagick responded: "It looks like this error message is created by
the mesa driver
20 matches
Mail list logo