DOCSLIB.ORG

AMD Codexl 1.1 GA Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
AMD Codexl 1.1 GA Release Notes AMD CodeXL 1.1 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use our CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: CodeXL Visual Studio 2012 and 2010 packages and Standalone application, for 32-bit and 64-bit Windows platforms CodeXL for 64-bit Linux platforms Kernel Analyzer v2 for both Windows and Linux platforms Note about 32-bit Windows CodeXL 1.1 Upgrade Error On 32-bit Windows platforms, upgrading from previous version of CodeXL using the CodeXL 1.1 installer will remove the previous version and then display an error message without installing CodeXL 1.1. The recommended method is to uninstall previous CodeXL before installing CodeXL 1.1. If you ran the 1.1 installer to upgrade a previous installation and encountered the error mentioned above, ignore the error and run the installer again to install CodeXL 1.1. Note about installing CodeAnalyst after installing CodeXL for Windows CodeXL can be safely installed on a Windows station where AMD CodeAnalyst is already installed. However, do not install CodeAnalyst on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5xxx or newer) or APU is required o The AMD Catalyst Driver must be installed, release 12.8 or later. Catalyst 13.1 is the recommended version. For GPU API-Level Debugging, a working OpenCL/OpenGL configuration is required (AMD or other). CPU Profiling o Time Based Profiling can be performed on any x86 or AMD64 (x86-64) CPU/APU. On Windows 8, only AMD CPUs/APUs are supported. o The Event Based Profiling (EBP) and Instruction Based Sampling (IBS) session types require an AMD CPU or APU processor. Supported platforms: Windows platforms o Windows 7 32-bit and 64-bit, Beta support for Windows 8 32-bit and 64-bit o Visual Studio 2010/2012 must be installed on the station before the CodeXL Visual Studio 2010/2012 Package is installed, respectively. Linux platforms o Red Hat EL 6 u2 64-bit o Ubuntu 12.04 64-bit New in this version The following items are new in this version: Beta support for Windows 8, 32 and 64 bit. Visual Studio 2012 integration Support for KDE desktop environment on supported Linux distributions OpenCL/OpenGL Debugger and Profiler Support for AMD’s Sea Island family of GPUs. CPU Profiler support-ready for AMD’s Kabini APUs User experience enhancements: o Mode Specific layouts display a sub-set of CodeXL views and toolbars that match the current mode – Debug or Profile. o Profile Session Explorer Tree and Debug Explorer Tree views are merged into a single view named CodeXL Explorer. o New design for Automatic Updates dialog Installation is now enabled for Windows platforms that are not formally supported. CodeXL may be installed on Windows Vista and Windows Server 2008 or later, although its function has not been verified on these platforms. Fixed Issues The following fixes were not part of the 1.0 release and are new to this version: Incorrect step-in order when debugging APP SDK MatrixMulImage sample (345842) – fixed in Catalyst 13.3 CodeXL crashes if you set a breakpoint at glUniformMatrix4fv (364063) When running CodeXL remotely on a Trinity platform with Ubuntu using putty/xming a segmentation fault is thrown (367512) – fixed in Catalyst 13.3 On Ubuntu systems, CodeXL may throw a segmentation fault while debugging the Teapot sample. (366589) CPU Profiler on RHEL6 U2, PERF has a known issue with Call Stack Ssampling (CSS) data on Time Based Profile run i.e. CSS data is not correctly shown for Time based profile run on RHEL6 U2. (355108, 359033) CodeXL crashes when debugging APP SDK sample MatrixTranspose on a FirePro W8000 or FirePro W9000 card (368026) – fixed in Catalyst 13.3 GPU Debugger - using certain OpenGL pixel formats for textures could cause crashes when viewing the texture images. GPU Profiler Performance Counters - Complete path and Fast path always report 0 on Caicos (352444) Global memory cannot be accessed by debugger when using Evergreen/Northern Islands and Catalyst 12.9 or later (370182) – fixed in Catalyst 13.1. GPU Profiler unresponsive during post-profile processing (343672) ‘Stop debugging’ button in toolbar is disabled after breakpoint hit in Visual Studio (352398) Drag&Drop is active while profiling/debugging in progress (353077) "Home Page | Recent projects" lists Teapot sample twice on Linux (354076) Two .cxl files are created when you open the Teapot example on Linux (354917) Log Files & image dir changes to "tmp" once you close Options window on Linux (355244) On Linux, CPU Profiler cannot start profile on invalid session import; Re-running CodeXL works (355804) CodeXL Customize tool bar Options shows Control names prefixed "cmdid" (356138) Floating point precision option should not contain 0 as list item on Linux (356155) Teapot sample loads for profiling session even if Debug mode is selected (356156) GPU Profiling BasicCompute11 sample won’t generate DirectX ASM (356471) Chars not allowed in filenames should not be in CodeXL project name (357501) The menu command ‘Profile Mode’ is not updated with session type in Visual Studio (357505) Toolbars embedded within views should be updated when mode changes (359173) CPU Profiler shows huge number of timer samples for shell script used to run FORTRAN app (361568) Cannot delete breakpoint set in code from Breakpoints window, after the debug session ends (362458) Breakpoints list in the Breakpoints dialog does not get updated on adding breakpoint from Function Call History view (362669) Step In after "glBindBuffers" breakpoint results in Catalyst Control Center crash (363176) "Show detailed batch statistics" button is always enabled (363463) Exported CSV file does not have column headings (363612) You should not be allowed to open a project while another project is being debug (364158) GPU Profiling options break after several profile sessions on Linux (366547) Incorrect directory structure in tarball prevents loading Teapot sources on Linux (368943) Profiling Teapot sample with Performance Counters using Catalyst 12.10 causes crash (369572) – fixed in Catalyst 13.1. Function Call History view shows only first letter of glStringMarkerGREMEDY arg (370015) KernelAnalyzer crashes on clicking "Build->Options" on a system with no discrete GPU installed (371005) CPU Profiler displays "unknown" column on Ubuntu Time based profile run (371373) GPU Debugger cannot evaluate value of a array element in watch (371502) Multiwatch view is broken if variable value active range is too large (371522) Shortcut F5 won't work when Execution Toolbar is hidden (371820) CPU Profiler "% of total session samples" data always shown wrong in module data view (372074) Installer displays "This action is only valid for products..." error after installation (372323) Observed Blue-Screen-Of-Death couple of times on windows7 32-bit machine while rebooting (372833) OpenGL function calls logging field in options window is not functional (372834) Known Issues CPU Profiling is disabled on Windows 8 and Windows Server 2012 platforms running on non- AMD CPUs. (385105) ‘Navigation to Source Code’ option is disabled for GPU Profiling Application Trace on Tahiti GPUs on Linux platforms. (376736) On Linux platforms with Cayman GPUs, if the screen saver locks the station after inactivity timeout during GPU Profiling Application Trace with ‘Enable Navigation to Source Code’ checked, the system cannot be unlocked. (376736) Debugging OpenCL kernels that use read-modify-write atomic operations is not supported. GPU Debugging on OpenCL Static C++ Kernels is not supported. (345852) __read_only and __write_only Image variables are not shown in locals during GPU Debugging. (345852) OpenCL 1.2 keyword printf is not supported during kernel debugging. Building kernels with OpenCL 1.2 clCreateProgramWithBinaries and clLinkProgram API prevents debugging these kernels. (369183) CPU profiling for managed code (OpenCL, OpenGL, Java, .Net …) is not supported. Module/Source information will not be available for managed code. Running CpuProfiling with Call-Stack Sampling (CSS) enabled, on systems with discrete graphics card (5000, 6000, 7000 series), may result in Linux kernel panic. This kernel panic does not occur with Linux kernel version 3.2 onwards. CPU Profiling on Linux platforms – Limitations of PERF o CPU profiling uses PERF which requires kernel 2.6.32 or later. CPU Profiling with Call Stack Sampling requires Linux kernel 3.0 or later. However, we recommend using kernel 3.2 and above which has shown to be more stable. o Call chain analysis on Linux currently depends on the call chain information provided by Linux PERF. This requires the profiled binaries to have stack frame pointer. (i.e. compiled with -fno-omit-frame-pointer). o For non-root users to run CodeXL CPU profiling, “/proc/sys/kernel/perf_event_paranoid” needs to be set to “-1”. o Instruction-Based Profiling on Linux requires Linux kernel 3.5 and above, and must be used with system-wide profiling. o Call chain information (stack trace) for inline functions is not available. Call Stack data collection may result in kernel panic on Ubuntu with kernel version 3.0 or lower. Workaround: Upgrade the Ubuntu kernel to 3.2 or above. (352399) PERF call chain which contains call stack across modules has shown to be truncated. This results in inaccurate "Deep Samples", "Downstream Samples", and "call path" analysis. Importing a thread based session generated from CodeAnalyst sometimes results in CodeXL crash. (356479) if gDEBugger is installed, mouse click doesn’t start text fields editing in CodeXL Visual Studio Extension. Workaround: Navigate to the text fields using TAB.
Load more

Recommended publications
  • An Introduction to Analysis and Optimization with AMD Codeanalyst™ Performance Analyzer
    An introduction to analysis and optimization with AMD CodeAnalyst™ Performance Analyzer Paul J. Drongowski AMD CodeAnalyst Team Advanced Micro Devices, Inc. Boston Design Center 8 September 2008 Introduction This technical note demonstrates how to use the AMD CodeAnalyst™ Performance Analyzer to analyze and improve the performance of a compute-bound program. The program that we chose for this demonstration is an old classic: matrix multiplication. We'll start with a "textbook" implementation of matrix multiply that has well-known memory access issues. We will measure and analyze its performance using AMD CodeAnalyst. Then, we will improve the performance of the program by changing its memory access pattern. 1. AMD CodeAnalyst AMD CodeAnalyst is a suite of performance analysis tools for AMD processors. Versions of AMD CodeAnalyst are available for both Microsoft® Windows® and Linux®. AMD CodeAnalyst may be downloaded (free of charge) from AMD Developer Central. (Go to http://developer.amd.com and click on CPU Tools.) Although we will use AMD CodeAnalyst for Windows in this tech note, engineers and developers can use the same techniques to analyze programs on Linux. AMD CodeAnalyst performs system-wide profiling and supports the analysis of both user applications and kernel- mode software. It provides five main types of data collection and analysis: • Time-based profiling (TBP), • Event-based profiling (EBP), • Instruction-based sampling (IBS), • Pipeline simulation (Windows-only feature), and • Thread profiling (Windows-only feature). We will look at the first three kinds of analysis in this note. Performance analysis usually begins with time-based profiling to identify the program hot spots that are candidates for optimization.
    [Show full text]
  • Amd Filed: February 24, 2009 (Period: December 27, 2008)
    FORM 10-K ADVANCED MICRO DEVICES INC - amd Filed: February 24, 2009 (period: December 27, 2008) Annual report which provides a comprehensive overview of the company for the past year Table of Contents 10-K - FORM 10-K PART I ITEM 1. 1 PART I ITEM 1. BUSINESS ITEM 1A. RISK FACTORS ITEM 1B. UNRESOLVED STAFF COMMENTS ITEM 2. PROPERTIES ITEM 3. LEGAL PROCEEDINGS ITEM 4. SUBMISSION OF MATTERS TO A VOTE OF SECURITY HOLDERS PART II ITEM 5. MARKET FOR REGISTRANT S COMMON EQUITY, RELATED STOCKHOLDER MATTERS AND ISSUER PURCHASES OF EQUITY SECURITIES ITEM 6. SELECTED FINANCIAL DATA ITEM 7. MANAGEMENT S DISCUSSION AND ANALYSIS OF FINANCIAL CONDITION AND RESULTS OF OPERATIONS ITEM 7A. QUANTITATIVE AND QUALITATIVE DISCLOSURE ABOUT MARKET RISK ITEM 8. FINANCIAL STATEMENTS AND SUPPLEMENTARY DATA ITEM 9. CHANGES IN AND DISAGREEMENTS WITH ACCOUNTANTS ON ACCOUNTING AND FINANCIAL DISCLOSURE ITEM 9A. CONTROLS AND PROCEDURES ITEM 9B. OTHER INFORMATION PART III ITEM 10. DIRECTORS, EXECUTIVE OFFICERS AND CORPORATE GOVERNANCE ITEM 11. EXECUTIVE COMPENSATION ITEM 12. SECURITY OWNERSHIP OF CERTAIN BENEFICIAL OWNERS AND MANAGEMENT AND RELATED STOCKHOLDER MATTERS ITEM 13. CERTAIN RELATIONSHIPS AND RELATED TRANSACTIONS AND DIRECTOR INDEPENDENCE ITEM 14. PRINCIPAL ACCOUNTANT FEES AND SERVICES PART IV ITEM 15. EXHIBITS, FINANCIAL STATEMENT SCHEDULES SIGNATURES EX-10.5(A) (OUTSIDE DIRECTOR EQUITY COMPENSATION POLICY) EX-10.19 (SEPARATION AGREEMENT AND GENERAL RELEASE) EX-21 (LIST OF AMD SUBSIDIARIES) EX-23.A (CONSENT OF ERNST YOUNG LLP - ADVANCED MICRO DEVICES) EX-23.B
    [Show full text]
  • Software Optimization Guide for Amd Family 15H Processors (.Pdf)
    Software Optimization Guide for AMD Family 15h Processors Publication No. Revision Date 47414 3.06 January 2012 Advanced Micro Devices © 2012 Advanced Micro Devices, Inc. All rights reserved. The contents of this document are provided in connection with Advanced Micro Devices, Inc. (“AMD”) products. AMD makes no representations or warranties with respect to the accuracy or completeness of the contents of this publication and reserves the right to make changes to specifications and product descriptions at any time without notice. The infor- mation contained herein may be of a preliminary or advance nature and is subject to change without notice. No license, whether express, implied, arising by estoppel or other- wise, to any intellectual property rights is granted by this publication. Except as set forth in AMD’s Standard Terms and Conditions of Sale, AMD assumes no liability whatsoever, and disclaims any express or implied warranty, relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particular purpose, or infringement of any intellectual property right. AMD’s products are not designed, intended, authorized or warranted for use as compo- nents in systems intended for surgical implant into the body, or in other applications intended to support or sustain life, or in any other application in which the failure of AMD’s product could create a situation where personal injury, death, or severe property or environmental damage may occur. AMD reserves the right to discontinue or make changes to its products at any time without notice. Trademarks AMD, the AMD Arrow logo, and combinations thereof, AMD Athlon, AMD Opteron, 3DNow!, AMD Virtualization and AMD-V are trademarks of Advanced Micro Devices, Inc.
    [Show full text]
  • Candidate Features for Future Opengl 5 / Direct3d 12 Hardware and Beyond 3 May 2014, Christophe Riccio
    Candidate features for future OpenGL 5 / Direct3D 12 hardware and beyond 3 May 2014, Christophe Riccio G-Truc Creation Table of contents TABLE OF CONTENTS 2 INTRODUCTION 4 1. DRAW SUBMISSION 6 1.1. GL_ARB_MULTI_DRAW_INDIRECT 6 1.2. GL_ARB_SHADER_DRAW_PARAMETERS 7 1.3. GL_ARB_INDIRECT_PARAMETERS 8 1.4. A SHADER CODE PATH PER DRAW IN A MULTI DRAW 8 1.5. SHADER INDEXED LOSE STATES 9 1.6. GL_NV_BINDLESS_MULTI_DRAW_INDIRECT 10 1.7. GL_AMD_INTERLEAVED_ELEMENTS 10 2. RESOURCES 11 2.1. GL_ARB_BINDLESS_TEXTURE 11 2.2. GL_NV_SHADER_BUFFER_LOAD AND GL_NV_SHADER_BUFFER_STORE 11 2.3. GL_ARB_SPARSE_TEXTURE 12 2.4. GL_AMD_SPARSE_TEXTURE 12 2.5. GL_AMD_SPARSE_TEXTURE_POOL 13 2.6. SEAMLESS TEXTURE STITCHING 13 2.7. 3D MEMORY LAYOUT FOR SPARSE 3D TEXTURES 13 2.8. SPARSE BUFFER 14 2.9. GL_KHR_TEXTURE_COMPRESSION_ASTC 14 2.10. GL_INTEL_MAP_TEXTURE 14 2.11. GL_ARB_SEAMLESS_CUBEMAP_PER_TEXTURE 15 2.12. DMA ENGINES 15 2.13. UNIFIED MEMORY 16 3. SHADER OPERATIONS 17 3.1. GL_ARB_SHADER_GROUP_VOTE 17 3.2. GL_NV_SHADER_THREAD_GROUP 17 3.3. GL_NV_SHADER_THREAD_SHUFFLE 17 3.4. GL_NV_SHADER_ATOMIC_FLOAT 18 3.5. GL_AMD_SHADER_ATOMIC_COUNTER_OPS 18 3.6. GL_ARB_COMPUTE_VARIABLE_GROUP_SIZE 18 3.7. MULTI COMPUTE DISPATCH 19 3.8. GL_NV_GPU_SHADER5 19 3.9. GL_AMD_GPU_SHADER_INT64 20 3.10. GL_AMD_GCN_SHADER 20 3.11. GL_NV_VERTEX_ATTRIB_INTEGER_64BIT 21 3.12. GL_AMD_ SHADER_TRINARY_MINMAX 21 4. FRAMEBUFFER 22 4.1. GL_AMD_SAMPLE_POSITIONS 22 4.2. GL_EXT_FRAMEBUFFER_MULTISAMPLE_BLIT_SCALED 22 4.3. GL_NV_MULTISAMPLE_COVERAGE AND GL_NV_FRAMEBUFFER_MULTISAMPLE_COVERAGE 22 4.4. GL_AMD_DEPTH_CLAMP_SEPARATE 22 5. BLENDING 23 5.1. GL_NV_TEXTURE_BARRIER 23 5.2. GL_EXT_SHADER_FRAMEBUFFER_FETCH (OPENGL ES) 23 5.3. GL_ARM_SHADER_FRAMEBUFFER_FETCH (OPENGL ES) 23 5.4. GL_ARM_SHADER_FRAMEBUFFER_FETCH_DEPTH_STENCIL (OPENGL ES) 23 5.5. GL_EXT_PIXEL_LOCAL_STORAGE (OPENGL ES) 24 5.6. TILE SHADING 25 5.7. GL_INTEL_FRAGMENT_SHADER_ORDERING 26 5.8. GL_KHR_BLEND_EQUATION_ADVANCED 26 5.9.
    [Show full text]
  • AMD Firepro™ W5000
    AMD FirePro™ W5000 Be Limitless, When Every Detail Counts. Powerful mid-range workstation graphics. This powerful product, designed for delivering superior performance for CAD/CAE and Media workflows, can process Key Features: up to 1.65 billion triangles per second. This means during > Utilizes Graphics Core Next (GCN) to the design process you can easily interact and render efficiently balance compute tasks with your 3D models, while the competition can only process 3D workloads, enabling multi-tasking that is designed to optimize utilization up to 0.41 billion triangles per second (up to four times and maximize performance. less performance). It also offers double the memory > Unmatched application of competing products (2GB vs. 1GB) and 2.5x responsiveness in your workflow, the memory bandwidth. It’s the ideal solution whether in advanced visualization, for professionals working with a broad range of complex models, large data sets or applications, moderately complex models and datasets, video editing. and advanced visual effects. > AMD ZeroCore Power Technology enables your GPU to power down when your monitor is off. Product features: > AMD ZeroCore Power technology leverages > GeometryBoost—the GPU processes > Optimized and certified for major CAD and M&E AMD’s leadership in notebook power efficiency geometry data at a rate of twice per clock cycle, doubling the rate of primitive applications delivering 1 TFLOP of single precision and 80 to enable our desktop GPUs to power down and vertex processing. GFLOPs of double precision performance with when your monitor is off, also known as the > AMD Eyefinity Technology— outstanding reliability for the most demanding “long idle state.” Industry-leading multi-display professional tasks.
    [Show full text]
  • AMD Firepro™Professional Graphics for CAD & Engineering and Media & Entertainment
    AMD FirePro™Professional Graphics for CAD & Engineering and Media & Entertainment Performance at every price point. AMD FirePro professional graphics offer breakthrough capabilities that can help maximize productivity and help lower cost and complexity — giving you the edge you need in your business. Outstanding graphics performance, compute power and ultrahigh-resolution multidisplay capabilities allows broadcast, design and engineering professionals to work at a whole new level of detail, speed, responsiveness and creativity. AMD FireProTM W9100 AMD FireProTM W8100 With 16GB GDDR5 memory and the ability to support up to six 4K The new AMD FirePro W8100 workstation graphics card is based on displays via six Mini DisplayPort outputs,1 the AMD FirePro W9100 the AMD Graphics Core Next (GCN) GPU architecture and packs up graphics card is the ideal single-GPU solution for the next generation to 4.2 TFLOPS of compute power to accelerate your projects beyond of ultrahigh-resolution visualization environments. just graphics. AMD FireProTM W7100 AMD FireProTM W5100 The new AMD FirePro W7100 graphics card delivers 8GB The new AMD FirePro™ W5100 graphics card delivers optimized of memory, application performance and special features application and multidisplay performance for midrange users. that media and entertainment and design and engineering With 4GB of ultra-fast GDDR5 memory, users can tackle moderately professionals need to take their projects to the next level. complex models, assemblies, data sets or advanced visual effects with ease. AMD FireProTM W4100 AMD FireProTM W2100 In a class of its own, the AMD FirePro Professional graphics starts with AMD W4100 graphics card is the best choice FirePro W2100 graphics, delivering for entry-level users who need a boost in optimized and certified professional graphics performance to better address application performance that similarly- their evolving workflows.
    [Show full text]
  • AMD Codexl 1.7 GA Release Notes
    AMD CodeXL 1.7 GA Release Notes Thank you for using CodeXL. We appreciate any feedback you have! Please use the CodeXL Forum to provide your feedback. You can also check out the Getting Started guide on the CodeXL Web Page and the latest CodeXL blog at AMD Developer Central - Blogs This version contains: For 64-bit Windows platforms o CodeXL Standalone application o CodeXL Microsoft® Visual Studio® 2010 extension o CodeXL Microsoft® Visual Studio® 2012 extension o CodeXL Microsoft® Visual Studio® 2013 extension o CodeXL Remote Agent For 64-bit Linux platforms o CodeXL Standalone application o CodeXL Remote Agent Note about installing CodeAnalyst after installing CodeXL for Windows AMD CodeAnalyst has reached End-of-Life status and has been replaced by AMD CodeXL. CodeXL installer will refuse to install on a Windows station where AMD CodeAnalyst is already installed. Nevertheless, if you would like to install CodeAnalyst, do not install it on a Windows station already installed with CodeXL. Uninstall CodeXL first, and then install CodeAnalyst. System Requirements CodeXL contains a host of development features with varying system requirements: GPU Profiling and OpenCL Kernel Debugging o An AMD GPU (Radeon HD 5000 series or newer, desktop or mobile version) or APU is required. o The AMD Catalyst Driver must be installed, release 13.11 or later. Catalyst 14.12 (driver 14.501) is the recommended version. See "Getting the latest Catalyst release" section below. For GPU API-Level Debugging, a working OpenCL/OpenGL configuration is required (AMD or other). CPU Profiling o Time-Based Profiling can be performed on any x86 or AMD64 (x86-64) CPU/APU.
    [Show full text]
  • Opengl ES, XNA, Directx for WP8) Plan
    Mobilne akceleratory grafiki Kamil Trzciński, 2013 O mnie Kamil Trzciński http://ayufan.eu / [email protected] ● Od 14 lat zajmuję się programowaniem (C/C++, Java, C#, Python, PHP, itd.) ● Od 10 lat zajmuję się programowaniem grafiki (OpenGL, DirectX 9/10/11, Ray-Tracing) ● Od 6 lat zajmuję się branżą mobilną (SymbianOS, Android, iOS) ● Od 2 lat zajmuję się mobilną grafiką (OpenGL ES, XNA, DirectX for WP8) Plan ● Bardzo krótko o historii ● Mobilne układy graficzne ● API ● Programowalne jednostki cieniowania ● Optymalizacja ● Silniki graficzne oraz silniki gier Wstęp Grafika komputerowa to dziedzina informatyki zajmująca się wykorzystaniem technik komputerowych do celów wizualizacji artystycznej oraz wizualizacji rzeczywistości. Bardzo często grafika komputerowa jest kojarzona z urządzeniem wspomagającym jej generowanie - kartą graficzną, odpowiedzialna za renderowanie grafiki oraz jej konwersję na sygnał zrozumiały dla wyświetlacza 1. Historia Historia Historia kart graficznych sięga wczesnych lat 80-tych ubiegłego wieku. Pierwsze karty graficzne potrafiły jedynie wyświetlać znaki alfabetu łacińskiego ze zdefiniowanego w pamięci generatora znaków, tzw. trybu tekstowego. W późniejszym okresie pojawiły się układy, wykonujące tzw. operacje BitBLT, pozwalające na nałożenie na siebie 2 różnych bitmap w postaci rastrowej. Historia Historia #2 ● Wraz z nadejściem systemu operacyjnego Microsoft Windows 3.0 wzrosło zapotrzebowanie na przetwarzanie grafiki rastrowej dużej rozdzielczości. ● Powstaje interfejs GDI odpowiedzialny za programowanie operacji związanych z grafiką. ● Krótko po tym powstały pierwsze akceleratory 2D wyprodukowane przez firmę S3. Wydarzenie to zapoczątkowało erę graficznych akceleratorów grafiki. Historia #3 ● 1996 – wprowadzenie chipsetu Voodoo Graphics przez firmę 3dfx, dodatkowej karty rozszerzeń pełniącej funkcję akceleratora grafiki 3D. ● Powstają biblioteki umożliwiające tworzenie trójwymiarowych wizualizacji: Direct3D oraz OpenGL. Historia #3 Historia #4 ● 1999/2000 – DirectX 7.0 dodaje obsługę: T&L (ang.
    [Show full text]
  • Media Kit 2019 Technology for Optimal Engineering Design
    MEDIA KIT 2019 TECHNOLOGY FOR OPTIMAL ENGINEERING DESIGN DigitalEngineering247.com Who We Are From the Publisher DE’S MISSION Welcome to Digital Engineering, a B2B media business dedicated to technology for optimal engineering The design engineer is in the center of a design. We have a dedicated following of over 88,000 design engineers and engineering & IT managers at the never-ending cycle of improvement that very front end of product design. DE’s targeted audience consumes our cutting-edge editorial content that is provided in the form of a magazine (print & digital formats), five e-newsletters, editorial webcasts and our relies on the integration of multiple redesigned website at www.DigitalEngineering247.com technologies, multi-disciplinary engineering Unlike other design engineering titles, we do not try to be all things to all people. We are not a component teams, and the collection and dissemination magazine. We focus on the technologies that drive better designs. We cover the following: of design, simulation, test and market • design software data. In addition to using the best available • simulation & analysis software technology to optimize each stage of the • prototyping options (additive/subtractive/short-run manufacturing) • test & measurement cycle, a fully optimized workflow enhances • IoT/sensors to communicate the data communication and collaboration along a • computer options (workstations/HPC/Cloud) to run the software and manage the data digital thread that connects the engineering • workflow software to communicate the design process throughout the entire lifecycle via the digital thread. team, colleagues in other departments, Please see the specific departments and product coverage on the next page.
    [Show full text]
  • GPU Rigid Body Simulation Using Opencl Erwin Coumans
    GPU rigid body simulation using OpenCL Erwin Coumans, http://bulletphysics.org Introduction This document discusses our efforts to rewrite our rigid body simulator, Bullet 3.x, to make it suitable for many-core systems, such as GPUs, using OpenCL. Although OpenCL is thought, most of it can be applied to projects using other GPU compute languages, such as NVIDIA CUDA and Microsoft DX11 Direct Compute. Bullet is physics simulation software, in particular for rigid body dynamics and collision detection in. The project started around 2003, as in-house physics engine for a Playstation 2 game. In 2005 it was made publically available as open source under a liberal zlib license. Since then it is being used by game developers, movie studios and 3d modelers and authoring tools such as Maya, Blender, Cinema 4D etc. Before the rewrite, we have been optimizing and refactoring Bullet 2.x for multi-code, and we’ll briefly touch on those efforts. Previously we have worked on simplified GPU rigid body simulation, such as [Harada 2010] and [Coumans 2009]. Our recent GPU rigid body dynamics work has approached the same quality compared to the CPU version. The Bullet 3.x rigid body and collision detection pipeline runs 100% on the GPU using OpenCL. On a high- end desktop GPU it can simulate 100 thousand rigid bodies in real-time. The source code is available as open source at http://github.com/erwincoumans/bullet3 . Appendix B shows how to build and use the project on Windows, Linux and Mac OSX. Bullet 2.x Refactoring Bullet 2.x is written in modular C++ and its API was initially designed to be flexible and extendible, rather than optimized for speed.
    [Show full text]
  • Catalyst™ Software Suite Version 9.5 Release Notes
    Catalyst™ Software Suite Version 9.5 Release Notes This release note provides information on the latest posting of AMD’s industry leading software suite, Catalyst™. This particular software suite updates both the AMD Display Driver, and the Catalyst™ Control Center. This unified driver has been further enhanced to provide the highest level of power, performance, and reliability. The AMD Catalyst™ software suite is the ultimate in performance and stability. For exclusive Catalyst™ updates follow Catalyst Maker on Twitter. This release note provides information on the following: z Web Content z AMD Product Support z Operating Systems Supported z New Features z Performance Improvements z Resolved Issues for the Windows Vista Operating System z Resolved Issues for the Windows XP Operating System z Resolved Issues for the Windows 7 Operating System z Known Issues Under the Windows Vista Operating System z Known Issues Under the Windows XP Operating System z Known Issues Under the Windows 7 Operating System z Installing the Catalyst™ Vista Software Driver z Catalyst™ Crew Driver Feedback ATI Catalyst™ Release Note Version 9.5 1 Web Content The Catalyst™ Software Suite 9.5 contains the following: z Radeon™ display driver 8.612 z HydraVision™ for both Windows XP and Vista z HydraVision™ Basic Edition (Windows XP only) z WDM Driver Install Bundle z Southbridge/IXP Driver z Catalyst™ Control Center Version 8.612 Caution: The Catalyst™ software driver and the Catalyst™ Control Center can be downloaded independently of each other. However, for maximum stability and performance AMD recommends that both components be updated from the same Catalyst™ release.
    [Show full text]
  • Porting Source to Linux
    Porting Source to Linux Valve’s Lessons Learned Overview . Who is this talk for? . Why port? . Windows->Linux . Linux Tools . Direct3D->OpenGL Why port? 100% Why port? Nov Dec Jan Feb . Linux is open 10% . Linux (for gaming) is growing, and quickly 1% . Stepping stone to mobile . Performance 0% . Steam for Linux Linux Mac Windows % December January February Windows 94.79 94.56 94.09 Mac 3.71 3.56 3.07 Linux 0.79 1.12 2.01 Why port? – cont’d . GL exposes functionality by hardware capability—not OS. China tends to have equivalent GPUs, but overwhelmingly still runs XP — OpenGL can allow DX10/DX11 (and beyond) features for all of those users Why port? – cont’d . Specifications are public. GL is owned by committee, membership is available to anyone with interest (and some, but not a lot, of $). GL can be extended quickly, starting with a single vendor. GL is extremely powerful Windows->Linux Windowing issues . Consider SDL! . Handles all cross-platform windowing issues, including on mobile OSes. Tight C implementation—everything you need, nothing you don’t. Used for all Valve ports, and Linux Steam http://www.libsdl.org/ Filesystem issues . Linux filesystems are case-sensitive . Windows is not . Not a big issue for deployment (because everyone ships packs of some sort) . But an issue during development, with loose files . Solution 1: Slam all assets to lower case, including directories, then tolower all file lookups (only adjust below root) . Solution 2: Build file cache, look for similarly named files Other issues . Bad Defines — E.g. Assuming that LINUX meant DEDICATED_SERVER .
    [Show full text]