DOCSLIB.ORG

Cross-Compiling Shading Languages

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cross-Compiling Shading Languages Cross-Compiling Shading Languages Masterthesis Lukas Hermanns KOM-M-0598 Fachbereich Elektrotechnik und Informationstechnik Fachbereich Informatik (Zweitmitglied) Fachgebiet Multimedia Kommunikation Prof. Dr.-Ing. Ralf Steinmetz Cross-Compiling Shading Languages Masterthesis KOM-M-0598 Submitted by Lukas Hermanns Day of submission: October 19, 2017 Consultant: Prof. Dr.-Ing. Ralf Steinmetz Supervisor: Robert Konrad Technische Universität Darmstadt Fachbereich Elektrotechnik und Informationstechnik Fachbereich Informatik (Zweitmitglied) Fachgebiet Multimedia Kommunikation (KOM) Prof. Dr.-Ing. Ralf Steinmetz Ehrenwörtliche Erklärung Hiermit versichere ich, die vorliegende Masterthesis ohne Hilfe Dritter und nur mit den angegebenen Quellen und Hilfsmitteln angefertigt zu haben. Alle Stellen, die aus den Quellen entnommen wurden, sind als solche kenntlich gemacht worden. Diese Arbeit hat in dieser oder ähnlicher Form noch keiner Prüfungsbehörde vorgelegen. Die schriftliche Fassung stimmt mit der elektronischen Fassung überein. Darmstadt, den 19. Oktober 2017 Lukas Hermanns i Abstract Shading languages are the major class of programming languages for a modern mainstream Graphics Processing Unit (GPU). The programs of those languages are called “Shaders” as they were originally used to describe shading characteristics for computer graphics applications. To make use of GPU accel- erated shaders a sophisticated rendering Application Programming Interface (API) is required and the available rendering APIs at the present time are OpenGL, Direct3D, Vulkan, and Metal. While Direct3D and Metal are only supported on a limited set of platforms, OpenGL and Vulkan are for the most part platform independent. On the one hand, Direct3D is the leading rendering API for many real-time graph- ics applications, especially in the video game industry. But on the other hand, OpenGL and Vulkan are the prevalent rendering APIs on mobile devices, especially for Android with the largest market share. Each rendering API has its own shading language which are very similar to each other but varying enough to make it difficult for developers to write a single shader to be used across multiple APIs. However, since the enormous appearance of mobile devices many graphics systems are reliant on being platform independent. Therefore, several rendering technologies must be provided as back ends. The naive approach is to write all shaders multiple times, i.e. once for each shading language which is error- prone, highly redundant, and difficult to maintain. This thesis investigates different approaches to automatically transform shaders from one high-level language into another, so called “cross-compilation” (sometimes also referred to as “trans-compilation”). High-level to high-level translation is reviewed as well as algorithms with an Intermediate Representation (IR) such as Standard Portable Intermediate Representation (SPIR-V). We are focusing the two most prevalent shading languages, which are firstly OpenGL Shading Language (GLSL) and secondly DirectX High Level Shading Language (HLSL), while Metal Shading Language (MSL) is only briefly examined. The benefits and failings of state-of-the-art approaches are clearly separated and a novel algorithm for generic shader cross-compilation is presented. 1 Acknowledgment First of all, I would like to thank my family for their support during my entire study. Through their support, they made many of the circumstances beside my study much easier. I would also like to thank Robert Konrad, who gave me the opportunity to base my thesis upon a long-term project in the research field of cross-platform development for real-time graphics applications. Finally, I would also like to thank Marko Pintera for his contribution to the XShaderCompiler project. 3 Contents 1 Introduction 7 1.1 Overview . .7 1.2 Motivation . .7 1.3 Outline . .8 2 Background 11 2.1 Shaders . 11 2.1.1 Language Feature Comparison . 15 2.2 Formal Languages . 16 2.2.1 Regular Expressions . 16 2.2.2 Pattern Systems . 17 2.2.3 Grammars . 17 2.3 Compilers . 19 2.3.1 Lexical Analyzer . 19 2.3.2 Abstract Syntax Tree . 20 2.3.3 Syntactic Analyzer . 21 2.3.4 Semantic Analyzer . 21 2.3.5 Control Flow Graph . 22 3 Related Work 23 3.1 Proceedings . 23 3.1.1 Macro Expansion . 23 3.1.2 Meta-Language & Graph-Based Shaders . 24 3.1.3 Byte-Code Decompiling . 25 3.1.4 Source-to-Source . 25 3.1.5 Intermediate Language . 27 3.2 Comparison . 29 4 Concept 31 4.1 Approach . 31 4.2 Investigation . 31 4.2.1 Matrix Ordering . 31 4.2.2 Matrix Subscript Swizzling . 32 4.2.3 Memory Packing Alignment . 33 4.2.4 Type Conversion . 35 4.2.5 Input and Output . 36 4.2.6 Intrinsics . 39 4.2.7 Attributes . 41 4.2.8 Buffer Objects . 43 4.2.9 Structures . 46 4.2.10 Member Functions . 48 4.2.11 Boolean Vector Expressions . 49 4.2.12 Name Mangling . 50 4.3 Restrictions . 51 5 5 Implementation 53 5.1 Front-End . 53 5.1.1 Uniform AST Design . 53 5.1.2 Generic Parsing . 57 5.1.3 Context Analysis . 59 5.2 Middle-End . 64 5.2.1 Transformation . 64 5.3 Back-End . 66 5.3.1 Code Generation . 66 6 Results and Discussion 69 6.1 Benchmarks . 69 6.1.1 Simple Texturing . 69 6.1.2 Compute Shader for Filtering . 71 6.1.3 Practical Shaders . 74 6.2 Performance Comparison . 75 7 Conclusion and Future Work 77 7.1 Conclusion . 77 7.2 Future Work . 77 7.3 Appendix . 77 Bibliography 78 6 Contents 1 Introduction 1.1 Overview In this thesis a novel method for cross-compiling shading languages is presented and compared to other state of the art approaches. The main focus is on the two mainstream shading languages HLSL and GLSL for real-time graphics applications. HLSL is the shading language of the Direct3D rendering API, while GLSL and its subtly modified dialect OpenGL ES Shading Language (ESSL) is the shading language for the OpenGL, OpenGL ES, and WebGL rendering APIs. There is also the modern shading language called “Metal” (or rather MSL) that is supported by the correspondent rendering API, but due to its limitation for products by Apple Inc. and the alternative of ESSL it is only briefly examined. Although Direct3D is only available on a limited set of platforms as well, more precisely on platforms provided by Microsoft Corporation, its large distribution in the video game industry makes HLSL a major candidate for cross-compilation. Although HLSL and GLSL have the same purpose and are quite similar in many ways, there are also lots of differences in both syntax and semantics. Even a very primitive shader program like shown in Listing 1.1 must be translated to something that looks quite different as shown in Listing 1.2, or vice versa. These two shaders both only pass the input vertex coordinate to the fragment shader. Listing 1.1: HLSL Listing 1.2: GLSL 1 struct v2f { 1 #version 130 2 float4 position : SV_Position; 2 in vec4 coord; 3 }; 3 void main() { 4 v2f VS(float4 coord : COORD) { 4 gl_Position = coord; 5 return (v2f)coord; 5 } 6 } This thesis covers different approaches to allow those shaders being written only once and to be used on multiple rendering APIs. These approaches reach from heavy macro meta-programming over simple parsers to full shader compilers. 1.2 Motivation Platform independence is a very important quality for a broad range of applications. This applies to end user applications that are meant to run on a variety of desktop and mobile platforms such as Windows, macOS, GNU/Linux, Android, and iOS as well as to middleware software that composes the foundation of such end user programs. In the situation of real-time graphics applications this requirement has changed in the recent years. Before the enormous appearance of mobile phones with 3D hardware acceleration (simply known as “smartphones”), the leading shading language was HLSL and its (now obsolete) dialect C for Graphics (Cg), which was developed by NVIDIA together with Microsoft [23, 34]. This was the case for at least the video game industry where HLSL (or Cg) was supported on the major gaming platforms: Microsoft® Windows, Microsoft® Xbox® 360, and Sony™ PlayStation® 3. In the field of research, GLSL was the prevalent shading language, due its platform independence on desktop computers. Though, since the market share of smartphones, especially those with Google Android and Apple iOS that do not sup- port HLSL at all, has grown rapidly, the importance to support multiple shading languages in graphics applications has increased. Because the naive approach of translating shader programs by hand is time consuming, error-prone, and hardly maintainable when shaders are altered or extended, an automatic translation of these pro- 7 grams is highly necessary. Since this problem is not new to the development process of platform in- dependent rendering systems, many different approaches and solutions exist throughout the web.
Load more

Recommended publications
  • GLSL 4.50 Spec
    The OpenGL® Shading Language Language Version: 4.50 Document Revision: 7 09-May-2017 Editor: John Kessenich, Google Version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost Copyright (c) 2008-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • Slang: Language Mechanisms for Extensible Real-Time Shading Systems
    Slang: language mechanisms for extensible real-time shading systems YONG HE, Carnegie Mellon University KAYVON FATAHALIAN, Stanford University TIM FOLEY, NVIDIA Designers of real-time rendering engines must balance the conicting goals and GPU eciently, and minimizing CPU overhead using the new of maintaining clear, extensible shading systems and achieving high render- parameter binding model oered by the modern Direct3D 12 and ing performance. In response, engine architects have established eective de- Vulkan graphics APIs. sign patterns for authoring shading systems, and developed engine-specic To help navigate the tension between performance and maintain- code synthesis tools, ranging from preprocessor hacking to domain-specic able/extensible code, engine architects have established eective shading languages, to productively implement these patterns. The problem is design patterns for authoring shading systems, and developed code that proprietary tools add signicant complexity to modern engines, lack ad- vanced language features, and create additional challenges for learning and synthesis tools, ranging from preprocessor hacking, to metapro- adoption. We argue that the advantages of engine-specic code generation gramming, to engine-proprietary domain-specic languages (DSLs) tools can be achieved using the underlying GPU shading language directly, [Tatarchuk and Tchou 2017], for implementing these patterns. For provided the shading language is extended with a small number of best- example, the idea of shader components [He et al. 2017] was recently practice principles from modern, well-established programming languages. presented as a pattern for achieving both high rendering perfor- We identify that adding generics with interface constraints, associated types, mance and maintainable code structure when specializing shader and interface/structure extensions to existing C-like GPU shading languages code to coarse-grained features such as a surface material pattern or enables real-time renderer developers to build shading systems that are a tessellation eect.
    [Show full text]
  • Opengl Shading Languag 2Nd Edition (Orange Book)
    OpenGL® Shading Language, Second Edition By Randi J. Rost ............................................... Publisher: Addison Wesley Professional Pub Date: January 25, 2006 Print ISBN-10: 0-321-33489-2 Print ISBN-13: 978-0-321-33489-3 Pages: 800 Table of Contents | Index "As the 'Red Book' is known to be the gold standard for OpenGL, the 'Orange Book' is considered to be the gold standard for the OpenGL Shading Language. With Randi's extensive knowledge of OpenGL and GLSL, you can be assured you will be learning from a graphics industry veteran. Within the pages of the second edition you can find topics from beginning shader development to advanced topics such as the spherical harmonic lighting model and more." David Tommeraasen, CEO/Programmer, Plasma Software "This will be the definitive guide for OpenGL shaders; no other book goes into this detail. Rost has done an excellent job at setting the stage for shader development, what the purpose is, how to do it, and how it all fits together. The book includes great examples and details, and good additional coverage of 2.0 changes!" Jeffery Galinovsky, Director of Emerging Market Platform Development, Intel Corporation "The coverage in this new edition of the book is pitched just right to help many new shader- writers get started, but with enough deep information for the 'old hands.'" Marc Olano, Assistant Professor, University of Maryland "This is a really great book on GLSLwell written and organized, very accessible, and with good real-world examples and sample code. The topics flow naturally and easily, explanatory code fragments are inserted in very logical places to illustrate concepts, and all in all, this book makes an excellent tutorial as well as a reference." John Carey, Chief Technology Officer, C.O.R.E.
    [Show full text]
  • Opengl 4.0 Shading Language Cookbook
    OpenGL 4.0 Shading Language Cookbook Over 60 highly focused, practical recipes to maximize your use of the OpenGL Shading Language David Wolff BIRMINGHAM - MUMBAI OpenGL 4.0 Shading Language Cookbook Copyright © 2011 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: July 2011 Production Reference: 1180711 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-849514-76-7 www.packtpub.com Cover Image by Fillipo ([email protected]) Credits Author Project Coordinator David Wolff Srimoyee Ghoshal Reviewers Proofreader Martin Christen Bernadette Watkins Nicolas Delalondre Indexer Markus Pabst Hemangini Bari Brandon Whitley Graphics Acquisition Editor Nilesh Mohite Usha Iyer Valentina J. D’silva Development Editor Production Coordinators Chris Rodrigues Kruthika Bangera Technical Editors Adline Swetha Jesuthas Kavita Iyer Cover Work Azharuddin Sheikh Kruthika Bangera Copy Editor Neha Shetty About the Author David Wolff is an associate professor in the Computer Science and Computer Engineering Department at Pacific Lutheran University (PLU).
    [Show full text]
  • Graphics Shaders Mike Hergaarden January 2011, VU Amsterdam
    Graphics shaders Mike Hergaarden January 2011, VU Amsterdam [Source: http://unity3d.com/support/documentation/Manual/Materials.html] Abstract Shaders are the key to finalizing any image rendering, be it computer games, images or movies. Shaders have greatly improved the output of computer generated media; from photo-realistic computer generated humans to more vivid cartoon movies. Furthermore shaders paved the way to general-purpose computation on GPU (GPGPU). This paper introduces shaders by discussing the theory and practice. Introduction A shader is a piece of code that is executed on the Graphics Processing Unit (GPU), usually found on a graphics card, to manipulate an image before it is drawn to the screen. Shaders allow for various kinds of rendering effect, ranging from adding an X-Ray view to adding cartoony outlines to rendering output. The history of shaders starts at LucasFilm in the early 1980’s. LucasFilm hired graphics programmers to computerize the special effects industry [1]. This proved a success for the film/ rendering industry, especially at Pixars Toy Story movie launch in 1995. RenderMan introduced the notion of Shaders; “The Renderman Shading Language allows material definitions of surfaces to be described in not only a simple manner, but also highly complex and custom manner using a C like language. Using this method as opposed to a pre-defined set of materials allows for complex procedural textures, new shading models and programmable lighting. Another thing that sets the renderers based on the RISpec apart from many other renderers, is the ability to output arbitrary variables as an image—surface normals, separate lighting passes and pretty much anything else can be output from the renderer in one pass.” [1] The term shader was first only used to refer to “pixel shaders”, but soon enough new uses of shaders such as vertex and geometry shaders were introduced, making the term shaders more general.
    [Show full text]
  • From a Programmable Pipeline to an Efficient Stream Processor
    Computation on GPUs: From a Programmable Pipeline to an Efficient Stream Processor João Luiz Dihl Comba 1 Carlos A. Dietrich1 Christian A. Pagot1 Carlos E. Scheidegger1 Resumo: O recente desenvolvimento de hardware gráfico apresenta uma mu- dança na implementação do pipeline gráfico, de um conjunto fixo de funções, para programas especiais desenvolvidos pelo usuário que são executados para cada vértice ou fragmento. Esta programabilidade permite implementações de diversos algoritmos diretamente no hardware gráfico. Neste tutorial serão apresentados as principais técnicas relacionadas a implementação de algoritmos desta forma. Serão usados exemplos baseados em artigos recentemente publicados. Através da revisão e análise da contribuição dos mesmos, iremos explicar as estratégias por trás do desenvolvimento de algoritmos desta forma, formando uma base que permita ao leitor criar seus próprios algoritmos. Palavras-chave: Hardware Gráfico Programável, GPU, Pipeline Gráfico Abstract: The recent development of graphics hardware is presenting a change in the implementation of the graphics pipeline, from a fixed set of functions, to user- developed special programs to be executed on a per-vertex or per-fragment basis. This programmability allows the efficient implementation of different algorithms directly on the graphics hardware. In this tutorial we will present the main techniques that are involved in implementing algorithms in this fashion. We use several test cases based on recently published pa- pers. By reviewing and analyzing their contribution, we explain the reasoning behind the development of the algorithms, establishing a common ground that allow readers to create their own novel algorithms. Keywords: Programmable Graphics Hardware, GPU, Graphics Pipeline 1UFRGS, Instituto de Informática, Caixa Postal 15064, 91501-970 Porto Alegre/RS, Brasil e-mail: {comba, cadietrich, capagot, carlossch}@inf.ufrgs.br Este trabalho foi parcialmente financiado pela CAPES, CNPq e FAPERGS.
    [Show full text]
  • The Opengl ES Shading Language
    The OpenGL ES® Shading Language Language Version: 3.20 Document Revision: 12 246 JuneAugust 2015 Editor: Robert J. Simpson, Qualcomm OpenGL GLSL editor: John Kessenich, LunarG GLSL version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost 1 Copyright (c) 2013-2015 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • 3D Graphics Technologies for Web Applications an Evaluation from the Perspective of a Real World Application
    Institutionen för systemteknik Department of Electrical Engineering Examensarbete 3D Graphics Technologies for Web Applications An Evaluation from the Perspective of a Real World Application Master thesis performed in information coding by Klara Waern´er LiTH-ISY-EX--12/4562--SE Link¨oping 2012-06-19 Department of Electrical Engineering Linköpings tekniska högskola Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping 3D Graphics Technologies for Web Applications An Evaluation from the Perspective of a Real World Application Master thesis in information coding at Link¨oping Institute of Technology by Klara Waern´er LiTH-ISY-EX--12/4562--SE Supervisors: Fredrik Bennet SICK IVP AB Jens Ogniewski ISY, Link¨opingUniversity Examiner: Ingemar Ragnemalm ISY, Link¨opingUniversity Link¨oping2012-06-19 Presentation Date Department and Division 2012-05-31 Department of Electrical Engineering Publishing Date (Electronic version) 2012-06-19 Language Type of Publication ISBN (Licentiate thesis) X English Licentiate thesis ISRN: LiTH-ISY-EX--12/4562--SE Other (specify below) X Degree thesis Thesis C-level Title of series (Licentiate thesis) Thesis D-level Report Number of Pages Other (specify below) Series number/ISSN (Licentiate thesis) 90 URL, Electronic Version http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-78726 Publication Title 3D Graphics Technologies for Web Applications: An Evaluation from the Perspective of a Real World Application Publication Title (Swedish) Tekniker för 3D-grafik i webbapplikationer: En utvärdering sedd utifrån en riktig applikations perspektiv Author(s) Klara Waernér Abstract Web applications are becoming increasingly sophisticated and functionality that was once exclusive to regular desktop applications can now be found in web applications as well.
    [Show full text]
  • "Shader Metaprogramming"
    An Embedded Shading Language by Zheng Qin A thesis presented to the University of Waterloo in fulfilment of the thesis requirement for the degree of Master of Mathematics in Computer Science Waterloo, Ontario, Canada, 2004 c Zheng Qin 2004 Author’s Declaration for Electronic Submission of a Thesis I hereby declare that I am the sole author of this thesis. This is a true copy of the thesis, including any required final revisions, as accepted by my examiners. I understand that my thesis may be made electronically available to the public. ii Abstract Modern graphics accelerators have embedded programmable components in the form of vertex and fragment shading units. Current APIs permit specification of the programs for these components using an assembly-language level interface. Compilers for high-level shading languages are available but these read in an exter- nal string specification, which can be inconvenient. It is possible, using standard C++, to define an embedded high-level shading language. Such a language can be nearly indistinguishable from a special-purpose shading language, yet permits more direct interaction with the specification of textures and parameters, simplifies implementation, and enables on-the-fly gener- ation, manipulation, and specification of shader programs. An embedded shading language also permits the lifting of C++ host language type, modularity, and scop- ing constructs into the shading language without any additional implementation effort. iii Acknowledgements I would like to thank my supervisor Michael D. McCool for his help throughout my study in Waterloo. I was always very excited by his continuous stream of new ideas. It was my great pleasure to study under his supervision.
    [Show full text]
  • Opengl Shading Language Course Chapter 1 – Introduction to GLSL By
    OpenGL Shading Language Course Chapter 1 – Introduction to GLSL By Jacobo Rodriguez Villar [email protected] TyphoonLabs’ GLSL Course 1/29 CHAPTER 1: INTRODUCTION INDEX An Introduction to Programmable Hardware 3 Brief History of the OpenGL Programmable Hardware Pipeline 3 Fixed Function vs. Programmable Function 5 Programmable Function Scheme 6 Fixed Function Scheme 7 Shader 'Input' Data 7 Uniform Variables 7 Vertex Attributes 9 Varying Variables 10 Shader 'Output' Data 12 Vertex Shader 12 Fragment Shader 12 Simple GLSL Shader Example 13 Shader Designer IDE 16 User Interface 16 Toolbar 17 Menu 17 State Properties 22 Light States 22 Vertex States 24 Fragment States 25 Code Window 26 Uniform Variables Manager 27 TyphoonLabs’ GLSL Course 2/29 An Introduction to Programmable Hardware Brief history of the OpenGL Programmable Hardware Pipeline 2000 Card(s) on the market: GeForce 2, Rage 128, WildCat, and Oxygen GVX1 These cards did not use any programmability within their pipeline. There were no vertex and pixel shaders or even texture shaders. The only programmatically think was the register combiners. Multi-texturing and additive blending were used to create clever effects and unique materials. 2001 Card(s) on the market: GeForce 3, Radeon 8500 With GeForce 3, NVIDIA introduced programmability into the vertex processing pipeline, allowing developers to write simple 'fixed-length' vertex programs using pseudo-assembler style code. Pixel processing was also improved with the texture shader, allowing more control over textures. ATI added similar functionality including some VS and FS extensions (EXT_vertex_shader and ATI_fragment_shader) Developers could now interpolate, modulate, replace, and decal between texture units, as well as extrapolate or combine with constant colors.
    [Show full text]
  • A Hardware-Aware Debugger for the Opengl Shading Language
    Graphics Hardware (2007) Timo Aila and Mark Segal (Editors) A Hardware-Aware Debugger for the OpenGL Shading Language Magnus Strengert, Thomas Klein, and Thomas Ertl Institute for Visualization and Interactive Systems Universität Stuttgart Abstract The enormous flexibility of the modern GPU rendering pipeline as well as the availability of high-level shader languages have led to an increased demand for sophisticated programming tools. As the application domain for GPU-based algorithms extends beyond traditional computer graphics, shader programs become more and more complex. The turn-around time for debugging, profiling, and optimizing GPU-based algorithms is now a critical factor in application development which is not addressed adequately by the tools available. In this paper we present a generic, minimal intrusive, and application-transparent solution for debugging OpenGL Shading Language programs, which for the first time fully supports GLSL 1.2 vertex and fragment shaders plus the recent geometry shader extension. By transparently instrumenting the shader program we retrieve information directly from the hardware pipeline and provide data for visual debugging and program analysis. Categories and Subject Descriptors (according to ACM CCS): I.3.4 [Computer Graphics]: Graphics Utilities – Soft- ware Support I.3.8 [Computer Graphics]: Methodology and Techniques – Languages D.2.5 [Software]: Software Engineering – Testing and Debugging 1. Introduction bugging and code analysis tools, did not keep up with the rapid advances of the hardware and software interface. As Graphics processing units have evolved into highly flex- a result, developers typically spend quite a large amount of ible, massively parallel computing architectures and have time locating and debugging programming errors.
    [Show full text]
  • Running on Raygun Arxiv:2001.09792V1 [Cs.GR]
    Running on Raygun Alexander Hirsch Peter Thoman With the introduction of Nvidia RTX hardware, ray tracing is now viable as a general real time rendering technique for complex 3D scenes. Leveraging this new technology, we present Raygun, an open source1 rendering, simulation, and game engine focusing on simplicity, expandability, and the topic of ray tracing realized through Nvidia’s Vulkan ray tracing extension. arXiv:2001.09792v1 [cs.GR] 27 Jan 2020 1 Introduction In the beginning, Nvidia RTX [7] could only be used via Nvidia OptiX [6], their dedicated ray tracing application framework, or via Microsoft DXR [5]. As many developers were hoping for a more open approach to this technology, Nvidia released an (experimental) extension for Vulkan [2] with their 411.63 graphics driver [9]. This advancement in technology is what makes Raygun possible. At the time consumers got their hands on Nvidia RTX capable graphics cards, none of the modern, publicly accessible video game engines allowed using Nvidia RTX for the whole rendering process. Initially we looked at Unity2, Unreal3, 1https://github.com/W4RH4WK/Raygun (MIT license) 2https://unity.com 3https://www.unrealengine.com 1 and Godot4 just to find out that RTX is not yet available in these engines. Unity’s engine is closed source, Unreal is far too large for us to add RTX support in a tangible amount of time, and Godot has not made the transition (from OpenGL) to Vulkan yet. This spawned the incipient idea of Raygun. While Quake II RTX [1], an implementation of RTX ray tracing using the Quake II engine, already existed at this time, we decided to create our own engine using C++ and modern libraries, focusing on a slim core with expandability in mind.
    [Show full text]