GCC Tips - Revision history

Tim Bird: /* Symbol Trace */

2012-01-10T18:46:38Z

‎Symbol Trace

2012-01-10T18:44:59Z

‎Print Pre-defined Macros: fix typo

2011-10-28T11:39:57Z

2011-10-27T22:53:20Z

2011-10-27T22:52:48Z

2011-10-04T17:39:59Z

‎Timing sub-commands

2011-10-04T17:33:24Z

2011-05-05T01:52:05Z

‎View Compilation Plan: Change style of quoted output to allow wrapping

2011-04-12T00:18:45Z

2011-04-12T00:18:17Z

@@ Line 218: / Line 218: @@
 </pre>
-This is very handy when you want to understand the linker is finding a definition of a symbol.  Some projects have name collisions or link order dependencies.  This lets you see precisely what the linker is doing.
+This is very handy when you want to understand where the linker is finding a definition of a symbol.  Some projects have name collisions or link order dependencies.  This lets you see precisely what the linker is doing.
 Given a hello world program, you would see output like

@@ Line 100: / Line 100: @@
 </pre>
-Very handy when porting code.  Lets you know if your target processor has some missing defines or if something is different (line __INT_MAX__) that can have interesting effects on your project.  Diff the output from the old to the new compiler so you can easily see the differences, makes it easy to spot problems before getting started.
+Very handy when porting code.  Lets you know if your target processor has some missing defines or if something is different (like __INT_MAX__) that can have interesting effects on your project.  Diff the output from the old to the new compiler so you can easily see the differences, makes it easy to spot problems before getting started.
 Sample output, from a compiler targeting an ARM processor.

@@ Line 238: / Line 238: @@
 [[Category:Development Tools]]
+[[Category: Tips and Tricks]]
 [[Category:Compiler]]

@@ Line 54: / Line 54: @@
 </pre>
-This was on a fast machine, with a very small sample program.  It shows that the sub-programs 'cc1', 'as', and 'collect2' (the pre-processor, the assembler, and the linker (collect2 is a front-end for 'ld'), respectively), took less than a few hundredths of a second each to run.
+This was on a fast machine, with a very small sample program.  It shows that the sub-programs 'cc1', 'as', and 'collect2' (the compiler, the assembler, and the linker (collect2 is a front-end for 'ld'), respectively), took less than a few hundredths of a second each to run.
 === Pre-Process, Retain Comments ===

@@ Line 41: / Line 41: @@
     elf32ppcsim
 </pre>
 === Pre-Process, Retain Comments ===

@@ Line 15: / Line 15: @@
 You can pipe this output to a file and execute that to compile a program, making it easy to experiment with tweaks to the linker or assembler.
-<pre>
+<pre style="white-space: pre-wrap;">
 Reading specs from /opt/timesys/toolchains/ppc7xx-linux/lib/gcc/powerpc-linux/3.4.1/specs
 Configured with: ../configure --prefix=/opt/timesys/toolchains/ppc7xx-linux --mandir=/opt/timesys/toolchains/ppc7xx-linux/share/man --infodir=/opt/timesys/toolchains/ppc7xx-linux/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++ --with-sysroot=/here/workdir/i386-x-ppc7xx/deleteme --disable-libgcj --build=i686-timesys-linux --host=i686-timesys-linux --target=powerpc-linux --program-prefix=ppc7xx-linux-

← Older revision		Revision as of 00:18, 12 April 2011
Line 223:		Line 223:
	The compilers temporary files are saved. This is often invaluable dealing with complicated makefiles to peek at the preprocessed output without having to figure out how to do a -E option by hand.		The compilers temporary files are saved. This is often invaluable dealing with complicated makefiles to peek at the preprocessed output without having to figure out how to do a -E option by hand.

−	[Category:Development Tools]	+	[[Category:Development Tools]]

← Older revision		Revision as of 00:18, 12 April 2011
Line 222:		Line 222:

	The compilers temporary files are saved. This is often invaluable dealing with complicated makefiles to peek at the preprocessed output without having to figure out how to do a -E option by hand.		The compilers temporary files are saved. This is often invaluable dealing with complicated makefiles to peek at the preprocessed output without having to figure out how to do a -E option by hand.
		+
		+	[Category:Development Tools]