Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

philippecp

philippecp philippecp

Niner since 2012

  • Defrag Tools #116 - PerfView Part 4

    Great talk overall however I have some questions regarding source code visualization. The concern about PDBs was glossed over in this talk but I'm still not clear how we configure them. I interpret Vance's comments that you don't need any configuration for Microsoft  code since it will automatically get it from the web. What I'm not clear is how do we get source code and relevant debug information for our own code. Do we need to have PDBs side by side with dlls on production server? Can we configure a PDB source path? Assuming we have a TFS source server, how do we configure PerfView to use it in order to retrieve right version of source for version deployed in production environment?

  • GoingNative 24: Microsoft Azure Storage Native Client Library: Tables and Queues

    Good video. One minor annoyance though is Gabriel's constant acknowledgement of the interviewee. When doing video interviews, it flows better from the viewer's point of view to have the interviewee not interrupted by "ok", "uh-huh", etc.

  • Browse the .NET Reference Source

    Is there any way to see extern methods like String.ReplaceInternal()?

  • Getting the most out of the C++ compiler

    @Charles:Great, that blog was exactly what I was looking for! Now if only an almighty moderator could add a link to this blog as a "see also" in the video description so that other curious minds that have had their interest piqued can dig deeper, that would be wonderful Wink

  • Getting the most out of the C++ compiler

    I find the title misleading. I was expecting some tips on how to write code in order to increase the likelihood of the compiler vectorizing a loop. Furthermore, I am left with the following questions:

    1. Does the array size need to be known at compile time?
    2. Do you need to use the index syntax (array[i]) or can you use pointers? What about iterators?
    3. Can the compiler vectorize operations on a std::vector<> ?
    4. Are there any operations that will prevent the compiler from vectorizing? ex. branching, trigonometry functions etc.
    5. If the compiler detects a cross-iteration dependency on one of the many operations in a loop, will it split the work in one vectorized loop and one scalar loop?