• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
quaikohc2

dx 11 hlsl, mapping source to assembly

5 posts in this topic

Hi,

In my simple shader editor i want to add the ability to look at shader's source code and corresponding assembly output for selected line or region. I know in a debug mode i can get line numbers in dissasembly but they are very innacurate (I have line 9 and next 20 for example). Anywas i want to have something similar i release mode. I know that code got reorganized a lot in the optimization process so this can be hard and it wont be accurate. Any ideas how to do this?

 

I guess it would be quite easy with volatile (is it still ignored by the compiler? was it ever working? why won't they just remove this keyword?). Do you know any other instruction I could use as a "marker". I mean it shouldn't do anything that would change normal shader execution and it shouldn't be optimized by a compiler so it's still visible in the assembly output?

 

 

cheers

Edited by quaikohc2
0

Share this post


Link to post
Share on other sites
Disable compiler optimization. There's simply no other way to get accurate source location information. D3DCOMPILE_DEBUG|D3DCOMPILE_OPTIMIZATION_LEVEL0. One does not automatically imply the other.
0

Share this post


Link to post
Share on other sites

As i said I know that, but these line numbers in debug assembly are not useful at all because they are so innacurate, not to mention it doesn't make sense to analyse debug assembly output. In c++ to analyse disasm in release mode i just used to put few volatile variables or __asm nop. Is there really nothing similar in hlsl?

Edited by quaikohc2
0

Share this post


Link to post
Share on other sites


In c++ to analyse disasm in release mode i just used to put few volatile variables or __asm nop. Is there really nothing similar in hlsl?
That's the same as disabling optimization -- it's not actually a release build any more if you do that, and you're still basically looking at a debug build...
1

Share this post


Link to post
Share on other sites

 


In c++ to analyse disasm in release mode i just used to put few volatile variables or __asm nop. Is there really nothing similar in hlsl?
That's the same as disabling optimization -- it's not actually a release build any more if you do that, and you're still basically looking at a debug build...

 

 

How is that? Why two volatile variables that are not used in the actual code would disable code optimization, e.g:

volatile int marker = 34;

 

for(int i = (etc etc)

(few lines of code here doing something important)

 

volatile int marker2 = 777;

0

Share this post


Link to post
Share on other sites

The HLSL compiler will aggressively inline, unroll, and reorder your code, much moreso than a C++ compiler. It can do this because the language is simple and generally free of side effects, and also because the virtual ISA provided by HLSL assembly is relatively simple. Anything you would do to prevent the compiler from doing this could potentially have a large effect on resulting performance, hence Hodgman's comment about it not actually being a Release build anymore.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0