imp/dump-build-information
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

fix h2 lines

Browse source
This commit is contained in:
Martin Errenst 2017-08-27 14:24:17 +02:00
parent 25115cb15d
commit 0a8fbdc588
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Readme.md
View file

@ -1,10 +1,10 @@
== Motivation ## Motivation
Print as much information about the build process as you can get from within the binary. Print as much information about the build process as you can get from within the binary.
Espacially, compiler flags - they are quite important when comparing performance. Espacially, compiler flags - they are quite important when comparing performance.
The information should be included in the binary, so it can't be lost and is right next to, for example, a benchmark result. The information should be included in the binary, so it can't be lost and is right next to, for example, a benchmark result.
So there's no chance to mix up different flags. So there's no chance to mix up different flags.
== Other options ## Other options
Another option would be -g -grecord-gcc-switches and search for DW_AT_producer. Another option would be -g -grecord-gcc-switches and search for DW_AT_producer.
Sadly, this doesn't produce the wanted information with clang: Sadly, this doesn't produce the wanted information with clang:
* clang++: DW_AT_producer : (indirect string, offset: 0x0): clang version 3.9.1 (tags/RELEASE_391/final) * clang++: DW_AT_producer : (indirect string, offset: 0x0): clang version 3.9.1 (tags/RELEASE_391/final)
@ -12,5 +12,5 @@ Sadly, this doesn't produce the wanted information with clang:
Passing the CPPFLAGS and so on as -DMY_FLAGS=.... to the compiler call will not include some information set by the compiler itself (compare the parameters set in the Makefile with the printed output). Passing the CPPFLAGS and so on as -DMY_FLAGS=.... to the compiler call will not include some information set by the compiler itself (compare the parameters set in the Makefile with the printed output).
== Known limitations ## Known limitations
* Works only with GCC for now. * Works only with GCC for now.