David Salinas comments

Results 30 comments of


                                            David Salinas

Call parameter type does not match function signature

Looking at this.

Call parameter type does not match function signature

So, I just tried to reproduce this error, building rocRAND, with latest HCC and HIP, and I couldn't reproduce the error you're seeing. But I'm not terribly surprised that you...

[BUG] Vector Reduce Example using Shared Memory is Wrongly Executed

@ghostplant : thanks. Just to keep you updated, we've opened an internal issue/bug report for this problem. We're investigating and will update this Issue.

Compile error on mcwamp_hsa

I'm assuming that you are building from latest clang_tot_upgrade branch, you will need to update/refresh your AMD HSA runtime (hsa-rocr-dev).

Compile error on mcwamp_hsa

sorry for not getting back to you sooner. Just do an "apt-get update" and then "apt-get upgrade". Is this still an issue for you with latest HCC ?

SSE2 Intrinsics cause compiler error

This is actually expected behaviour. Those builtins are only available for intel targets. HCC is a single-source CPU/GPU compiler. So there are two passes; one for CPU (host) and one...

libmcwamp_hsa.so: undefined symbol: KalmarContext* getContext()

KalmarContext* getContext() is defined in lib/mcwamp.cpp and libmcwamp.so. How are invoking HCC ?

libmcwamp_hsa.so has an executable stack

@AlexVlx @scchan @whchung Do any of you recall if we need to have an exec stack in mcwamp.o? I can try to add -noexecstack to our build of mcwamp.cpp and...

libmcwamp_hsa.so has an executable stack

@tstellar This just seems like the default (on ubuntu for ELF), unless we explicitly remove the exec stack from mcwamp.o. Do you have concerns with the exec stack being there?

libmcwamp_hsa.so has an executable stack

@tstellar sorry for the delay. So, I believe this is an artifact of default Clang behaviour. I'm trying to see if this can be disabled by default.