Merge pull request #41 from rainers/master

Visual D 0.3.41 beta3

Author: rainers

CHANGES

@@ -717,10 +717,13 @@ unreleased Version 0.3.41
   * cv2pdb:
     - improvements for DWARF conversion
   * dparser updated to cf26dbe426b10957f6364313cc7121e41083bebe with support for new 
-    language features in dmd 2.067
+    language features in dmd 2.067 and fixing a number of exceptions
   * some initial support for finding symbol references
   * new linker option "build and use local phobos library" to get a COFF32 version (dmd 2.067+)
     or add missing debug info (dmd 2.065+)
   * renaming project configuration did not change respective config on all platforms 
   * workaround for link response file with spaces, but disabled short names on NTFS volume
-  * profiler window: non-D symbols (e.g. C++ mangled functions) are no longer displayed empty
+  * profiler window: non-D symbols (e.g. C++ mangled functions) are no longer displayed empty
+  * new command "Compile and Disassemble" to show the disassembly of the current file in
+    the code context window that is automatically synchronized with editor movements
+

Makefile

@@ -155,6 +155,7 @@ mago:
 cv2pdb:
 	cd ..\..\cv2pdb\trunk && devenv /Project "cv2pdb"      /Build "Release|Win32" src\cv2pdb_vs12.sln
 	cd ..\..\cv2pdb\trunk && devenv /Project "dviewhelper" /Build "Release|Win32" src\cv2pdb_vs12.sln
+	cd ..\..\cv2pdb\trunk && devenv /Project "dumplines"   /Build "Release|Win32" src\cv2pdb_vs12.sln
 
 ##################################
 # create installer

TODO

@@ -40,6 +40,7 @@ Project:
 - VS2013: property pages don't follow resize
 - custom command: writes build batch to source folder
 - VS2013: possible to copy a project item with DnD into the same project again
+- saving file while it is being compiled/linked does not force a recompilation
 
 Language service:
 -----------------

VERSION

@@ -2,4 +2,4 @@
 #define VERSION_MINOR      3
 #define VERSION_REVISION   41
 #define VERSION_BETA       -beta
-#define VERSION_BUILD      2
+#define VERSION_BUILD      3

doc/CompileCommands.dd

@@ -0,0 +1,120 @@
+Ddoc
+
+$(P There are a number of commands in the Visual D menu that allow you to work with
+a single D source file without creating a project.)
+
+$(IMG_CENTER images/compilemenu.png)
+
+$(H2 Compile and Run)
+
+$(P This command will compile the current text window that has the edit focus. Compile options
+are taken from the active project configuration if the file is part of a project in the current solution.
+In addition options given in the $(LINK2 GlobalOptions.html, global settings) are added to the command
+line. Instead of building the full project, $(LINK2 http://dlang.org/rdmd.html, rdmd) is used
+to just add the minimal dependent modules. In order to build a runnable exectuable, you might have to add
+a $(D main) function to the source file or add $(D -main) to the global options. 
+)
+
+$(P One use case for this feature is to run unittests of a single module. Compilation errors, program output 
+and exception trace will be visible in the output window and can be double clicked to jump to the shown 
+code locations.
+)
+
+$(P When used on a source file not found in any of the projects in the solution, default options
+from the ConsoleApp project template are used to build the executable with rdmd. This allows script
+like usage of D files from within the IDE, though there is currently no way to specify execution
+arguments.
+)
+
+$(H2 Compile and Debug)
+
+$(P This command is similar to "Compile and Run", but instead of running the compiled executable
+immediately, the debugger is started to allow further inspection. If you want to trace execution from
+the very beginning of the program, you should set a breakpoint at the start of $(D main) before
+issuing this command.
+)
+
+$(H2 Compile and Disassemble)
+
+$(P While optimizing code, it is often useful to take a look at the assembly generated by the
+compiler. This is usually done by compiling a program, starting it in a debugger until it
+hits an appropriate breakpoint. The disassembly view will then show the desired machine 
+instructions.
+)
+
+$(P This can be a tedious and time consuming process, when all you want to look at is the
+disassembly of the currently written lines of code. The "Compile and Disassemble" command
+can take the pain out of this workflow, as it will just compile (not link) the current module
+with the command line options of the active project configuration and then show a
+disassembly dump in the Code Definition Window. It automatically synchronizes the instructions
+shown in the disassembly with the current caret location in the editor.
+)
+
+$(IMG_CENTER images/compiledisasm.png)
+
+$(P Dumping the assembly of an object file is done by an external command line tool that can 
+be configured for each tool chain in the $(LINK2 GlobalOptions.html, global settings). 
+For Win32, the generated object file format is rather dated OMF that is not very well 
+supported anymore. The commercial version of the Digital Mars C++ compiler contains
+the command line tool $(LINK2 http://www.digitalmars.com/ctg/obj2asm.html, obj2asm),
+but you can also use $(LINK2 http://www.agner.org/optimize/#objconv, objconv) by Agner Fog.
+For any other target or compiler platform, the generated object file format is COFF, that
+can be disassembled with the Microsoft tool $(D dumpbin) that comes with Visual Studio. In
+case you use Visual D to cross compile for other architectures with LDC or GDC, you might
+have to run the appropriate tools from these compiler suites instead.
+)
+
+$(P These are working settings for the "Disassemble Command" option, but you might want to
+tweak these for different output, e.g. switch between AT&T and Intel style assembly.
+Make sure that instruction offsets are displayed so synchronization with the
+editor works with the help of debug line number information.
+)
+
+$(H3 DMD/Win32)
+
+$(PRE obj2asm -x "$(DOLLAR)(InputFile)" >"$(DOLLAR)(TargetPath)")
+
+This assumes obj2asm can be found in through PATH. If this is not the case, please add
+the full path to it. The same replacement macros can be used as in the project 
+configurations.
+
+For objconv, this command is
+
+$(PRE obj2conv -fasm "$(DOLLAR)(InputFile)" "$(DOLLAR)(TargetPath)")
+
+$(H3 DMD/Win64)
+
+$(PRE "$(DOLLAR)(VCInstallDir)\bin\amd64\dumpbin" /disasm "$(DOLLAR)(InputPath)" >"$(DOLLAR)(TargetPath)" )
+
+$(H3 DMD/Win32-COFF)
+
+dumpbin executables can be used for both architectures x86 and AMD64, no matter
+what architecture might be running on, so you can use the same setting as Win64, 
+but in case you are restricted to a 32-bit OS, the respective executable can be 
+found in the bin folder of the VC installation:
+
+$(PRE "$(DOLLAR)(VCInstallDir)\bin\dumpbin" /disasm "$(DOLLAR)(InputPath)" >"$(DOLLAR)(TargetPath)" )
+
+There is one gotcha: dumpbin needs a DLL for doing the disassembly that is installed
+to $(VSInstallDir)\Common7\IDE (in VS 2013), so make sure you have this directory
+listed in the "Executable Paths".
+
+$(H3 LDC)
+
+dumpbin works here, too, for the x64/AMD64 architecture, but in case you want to
+use LLVM tools for other architectures, you'll have to change the default setting:
+
+$(PRE llvm-objdump -disassemble "$(DOLLAR)(InputPath)" >"$(DOLLAR)(TargetPath)" )
+
+You'll have to add the path the LLVM tools to the "Executable Paths" or to the
+llvm-objdump command.
+
+$(H3 GDC)
+
+Similar to LDC, the alternative command is
+
+$(PRE objdump --disassemble "$(DOLLAR)(InputPath)" >"$(DOLLAR)(TargetPath)" )
+
+Macros:
+	TITLE=Compile Commands
+

doc/build_doc.bat

@@ -22,6 +22,7 @@ set SRC=%SRC% GlobalOptions.dd
 set SRC=%SRC% Features.dd
 set SRC=%SRC% VersionHistory.dd
 set SRC=%SRC% News36.dd
+set SRC=%SRC% CompileCommands.dd
 
 set DDOC=macros.ddoc html.ddoc visuald.ddoc dlang.org.ddoc
 

doc/images/compiledisasm.png

@@ -395,6 +395,7 @@ ${MementoSection} "cv2pdb" SecCv2pdb
   ${File} ..\..\..\cv2pdb\trunk\ autoexp.visualizer
   ${File} ..\..\..\cv2pdb\trunk\bin\Release\ cv2pdb.exe
   ${File} ..\..\..\cv2pdb\trunk\bin\Release\ dviewhelper.dll
+  ${File} ..\..\..\cv2pdb\trunk\bin\Release\ dumplines.exe
   ${File} ..\..\..\cv2pdb\trunk\ README
   ${File} ..\..\..\cv2pdb\trunk\ LICENSE
   ${File} ..\..\..\cv2pdb\trunk\ CHANGES

doc/images/compilemenu.png

@@ -4,9 +4,14 @@ public import sdk.port.base;
 public import sdk.win32.unknwn;
 
 // VSI specifics
-__gshared IUnknown DOCDATAEXISTING_UNKNOWN;
+@property IUnknown DOCDATAEXISTING_UNKNOWN() 
+{
+	IUnknown unk;
+	*cast(size_t*)&unk = -1;
+	return unk;
+}
 
-shared static this() { *cast(int*)&DOCDATAEXISTING_UNKNOWN = -1; }
+//shared static this() { *cast(int*)&DOCDATAEXISTING_UNKNOWN = -1; }
 
 const GUID GUID_COMPlusNativeEng = { 0x92EF0900, 0x2251, 0x11D2, [ 0xB7, 0x2E, 0x00, 0x00, 0xF8, 0x75, 0x72, 0xEF ] };
 const GUID GUID_COMPlusOnlyEnd = uuid("{449EC4CC-30D2-4032-9256-EE18EB41B62B}");