1. 18 10月, 2015 4 次提交
  2. 25 9月, 2015 2 次提交
  3. 21 9月, 2015 2 次提交
  4. 16 9月, 2015 1 次提交
  5. 12 9月, 2015 1 次提交
  6. 11 9月, 2015 13 次提交
  7. 09 9月, 2015 1 次提交
  8. 05 9月, 2015 6 次提交
  9. 04 9月, 2015 3 次提交
  10. 28 8月, 2015 2 次提交
    • R
      scripts: add stackdelta script · 5bbb9f75
      Rasmus Villemoes 提交于
      This adds a simple perl script for reading two files as produced by
      the stackusage script and computing the changes in stack usage. For
      example:
      
      $ scripts/stackusage -o /tmp/old.su CC=gcc-4.7 -j8 fs/ext4/
      $ scripts/stackusage -o /tmp/new.su CC=gcc-5.0 -j8 fs/ext4/
      $ scripts/stackdelta /tmp/{old,new}.su | sort -k5,5g
      
      shows that gcc 5.0 generally produces less stack-hungry code than gcc
      4.7. Obviously, the script can also be used for measuring the effect
      of commits, .config tweaks or whatnot.
      Signed-off-by: NRasmus Villemoes <linux@rasmusvillemoes.dk>
      Signed-off-by: NMichal Marek <mmarek@suse.com>
      5bbb9f75
    • R
      scripts: add stackusage script · 56d4a381
      Rasmus Villemoes 提交于
      The current checkstack.pl script has a few problems, stemming from the
      overly simplistic attempt at parsing objdump output with regular
      expressions: For example, on x86_64 it doesn't take the push
      instruction into account, making it consistently underestimate the
      real stack use, and it also doesn't capture stack pointer adjustments
      of exactly 128 bytes [1].
      
      Since newer gcc (>= 4.6) knows about -fstack-usage, we might as well
      take the information straight from the horse's mouth. This patch
      introduces scripts/stackusage, which is a simple wrapper for running
      make with KCFLAGS set to -fstack-usage. Example use is
      
      scripts/stackusage -o out.su -j8 lib/
      
      The script understands "-o foo" for writing to 'foo' and -h for a
      trivial help text; anything else is passed to make.
      
      Afterwards, we find all newly created .su files, massage them a
      little, sort by stack use and write the result to a single output
      file.
      
      Note that the function names printed by (at least) gcc 4.7 are
      sometimes useless. For example, the first three lines of out.su
      generated above are
      
      ./lib/decompress_bunzip2.c:155  get_next_block  448     static
      ./lib/decompress_unlzma.c:537   unlzma  336     static
      ./lib/vsprintf.c:616    8       304     static
      
      That function '8' is really the static symbol_string(), but it has
      been subject to 'interprocedural scalar replacement of aggregates', so
      its name in the object file is 'symbol_string.isra.8'. gcc 5.0 doesn't
      have this problem; it uses the full name as seen in the object file.
      
      [1] Since gcc encodes that by
      
      48 83 c4 80             add    $0xffffffffffffff80,%rsp
      
      and not
      
      48 81 ec 80 00 00 00    sub    $0x80,%rsp
      
      since -128 fits in an imm8.
      Signed-off-by: NRasmus Villemoes <linux@rasmusvillemoes.dk>
      Signed-off-by: NMichal Marek <mmarek@suse.com>
      56d4a381
  11. 27 8月, 2015 1 次提交
  12. 26 8月, 2015 1 次提交
  13. 24 8月, 2015 3 次提交