Update faq

[parbenc]

No description provided.

[neon60]

Probably we should add these here:
https://advanced-micro-devices-demo--3622.com.readthedocs.build/projects/HIP/en/3622/understand/compilers.html

[MKKnorr]

I would have to rebase on top of that. Let's wait until either is merged in and add it to the other one

[neon60]

This should be in the porting guide and we should link here.

[MKKnorr]

I think this does not (only) belong to the porting guide, this is also relevant for other users. So either the programming guide, the compilers. I'd vote for the compilers or somewhere where we explain the compilation process.

[neon60]

Please link this tutorial: https://rocm.docs.amd.com/projects/HIP/en/latest/tutorial/saxpy.html#compiling-on-the-command-line

It is written to represent the compiler usage on different OS or platform.

[MKKnorr]

I was thinking of whether to even keep this question in the FAQ. That tutorial is a bit overkill for this question. Maybe something similar can also be added to the HIP compilers page of #3622 and we could link to that

[jujiang-del]

This tittle should be removed.

[MKKnorr]

I changed it. Removing it would expand the dynamic table of contents on the right side too much, and it's also not directly related to "HIP support"

[jujiang-del]

Sure

[jujiang-del]

HIP applications can be used on both AMD platform and non-AMD platform, like NVIDIA, using the conversion tool HIPIFY.

[MKKnorr]

This logic is backwards - CUDA code can be ported to the (portable) HIP code using HIPIFY. Also the question itself already implies, that the code can also run on NVIDIA platforms.

[jujiang-del]

For this question, I think the original explanation is better. User needs to know how to differentiate the platform, not how to port the code.

[MKKnorr]

The goal for this PR is to reduce the amount of content duplication, so where possible it is preferred to link to existing documentation. I found a better explanation in the hipcc documentation

[jujiang-del]

I think a question need to add "Can I develop applications with HIP APIs on Windows the same on Linux?"

[MKKnorr]

Is that really a frequently asked question? What would the answer to that be?

[jujiang-del]

FAQ looks good to me.

[jamesxu2]

@parbenc @MKKnorr

Some unintended consequences of the .md to .rst change that I just noticed are live:

Single backticks produce italics, instead of unformatted blocks. Here is an example - HIP_PLATFORM is now rendered as HIP_PLATFORM (ref)

Also, these nested bullet points got messed up and rendered as a single line

HIP provides * pointers and host-side pointer arithmetic. * device-level control over memory allocation and placement. * an offline compilation model.

(ref)