Public-Shader-Dokumentation der HD-5000-Reihe.

[Avalox]

AMD hat gestern eine detaillierte Dokumentation der Shader Funktionalität der Radeon HD 5000 Reihe veröffentlicht.

http://www.phoronix.com/scan.php?page=news_item&px=NzgzMg

[Gast]

direkter Link:

http://developer.amd.com/gpu/ATIStreamSDK/assets/AMD_Evergreen-Family_ISA_Instructions_and_Microcode.pdf

[mapel110]

Differences Between the R700-Family and Evergreen-Family of Devices

The following bullets provide a brief overview of the more important differences
between the R700-family and the Evergreen-family of GPUs.


Pixel parameter interpolation is now performed in kernel code, rather than in fixed-function hardware. Parameter data is preloaded into the local data share (LDS) before a pixel wavefront launch, and the kernel uses new INTERP_* instructions to evaluate a primitive’s vertex attribute value of each pixel.
Texture and vertex fetch clauses are now defined by which cache (TC or VC) services the clause, rather than by fetch-type.
Local data share (LDS) is now accessed through ALU instructions, rather than fetch instructions.
Added support for jump-tables.
Added the ability to write from a maximum of four streams to a maximum of four stream-out buffers.
Added support for flexible DX11 tesselation using hull shaders (HS) and domain shaders (DS).
Added thread-group synchronization in hardware for compute shaders (CS).
Added support to dynamically index texture resources, texture samplers, and ALU constant buffers.
Removed the Fbuffer and the Reduction buffer.
Added support for floating point rounding and denormal modes.
ALU clauses can now use up to four constant buffers using the
ALU_EXTENDED opcode.
Added support for exception flag collection.
Added thread tracing, whereby important events for each wavefront, for register writes, and for pipeline events are stored as descriptive tokens in a buffer.
Added single-step control of the control flow, allowing instructions to be
issued through register writes to the SQ, as well as arbitrary instructions to
be inserted in the execution path.


Ist damit immer noch DER F-Buffer von R350/R360 gemeint?! O_o

[mrt]

Es wird so einiges aus Kompatibilitätsgründen mitgeschleppt ;)