PCTuning fórum

• DirectX: AutoCAD 2013, 2D
• DirectX: AutoCAD 2013, 3D
• DirectX: Autodesk Inventor
• OpenGL: Maya 2013
• OpenGL: CATIA And EnSight
• OpenGL: LightWave And Maya
• OpenGL: Pro/ENGINEER And SolidWorks
• OpenGL: TcVis And NX
• OpenGL: Unigine Heaven
• OpenGL: Unigine Sanctuary
• OpenGL: Unigine Tropics
• OpenGL: PostFX And TessMark
• CUDA: 3ds Max + iray Renderer
• CUDA: Blender
• CUDA: Octane
• CUDA: FluidMark 1080p
• OpenCL: Bitmining, LuxMark, And ratGPU
• OpenCL: Computational Operations
• OpenCL: Image Processing
• OpenCL: Video Processing

Krteq píše:AMD se svými embedded a semi-custom rešeními expanduje i do leteckého průmyslu

AMD to Enter the Aerospace Industry with CoreAVI Avionics Technology

AMD tímto vydala Radeony PRO WX 4100, WX 5100 a WX 7100. Na tom by nebylo nic zvláštního, přislíbila to již v červnu. Jenže finální specifikace jsou výrazně lepší než původní červnové…

Using the HIPify Tools for automatic conversion, AMD was able to translate 99.6% of the code automatically. This is admittedly less than 100% – AMD has been upfront before that they may always be playing catch-up and won’t necessarily be able to replicate NVIDIA driver features 1-for-1 – but it’s significant progress. Ultimately AMD was able to finish the feature-complete port in less than 4 days for a 55K line project. And words can’t stress how important this is for AMD

• AMD Continues to Wow Investors With New Alibaba Collaboration
• AMD Radeon Technology Will Be Available on Google Cloud Platform in 2017

99.6% success
Overall the CAFFE port was quite successful – 99.6% of the code was either automatically ported or was automatically converted. A single developer required less than a week to clean up the remaining 200 lines of code to produce a working version on ROCm. Previously we have tried to use OpenCL C-based API to port similar C++ applications. Porting C++ to C is quite a challenging problem, and the OpenCL CAFFE port in fact required tens of thousands of additional lines of code. Much of this code duplicates the CUDA kernels and runtime, and so significantly increases the maintenance cost. In comparison, the HIP port is a small delta from the original code, the conversion is largely automated, and as we will see can replace the CUDA port. The HIP port also includes all the features of the original application, including the multi-GPU, optimized peer-to-peer communication, and CUDNN support.