1. 14 Jul, 2010 1 commit
    • Andi Kleen's avatar
      Kbuild: Add option to set -femit-struct-debug-baseonly · d6f4ceb7
      Andi Kleen authored
      Newer gcc has a -femit-struct-debug-baseonly option that dramatically
      reduces the size of object files with debug info. What it does
      is to only emit type information for structures when the structures
      are defined in the same file or in a header file.
      
      This means the type information for most headers are not included.
      This is not good when the type information is actually
      needed (e.g. with kgdb or systemtap)
      
      But often kernel hackers only care about line numbers and don't
      need all the type information anyways. In this case setting
      the option can be a big win:
      
      A build dir for a specific x86-64 configuration with gcc 4.5
      shrunk from 2.3G to 1.2G. The compilation was also nearly a minute
      faster.
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      [mmarek: reformatted help text]
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      d6f4ceb7
  2. 29 Jun, 2010 1 commit
  3. 18 Jun, 2010 2 commits
  4. 04 Jun, 2010 1 commit
    • Don Zickus's avatar
      Makefile.build: make KBUILD_SYMTYPES work again · e26d6b83
      Don Zickus authored
      commit 37a8d9f6 tried to combine some
      duplicate code and accidentally broke how KBUILD_SYMTYPES worked
      
      This fixes the code to match the original intention by the author who
      originally added the code I believe.
      
      The fixes include:
      - removing extra whitespaces in the if-statements
      - moving the if-statement from around the -r to the -T
      - adding a second arg to cmd_gensymtypes to simplify the options passed
        to genksyms.
      
      Tested by instrumenting genksyms and seeing what options were passed in
      during a make, KBUILD_SYMTYPES make, and when a foo.symref was created.
      
      Everything compiled and looked ok.
      Signed-off-by: default avatarDon Zickus <dzickus@redhat.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      e26d6b83
  5. 27 May, 2010 1 commit
  6. 06 May, 2010 1 commit
  7. 14 Apr, 2010 6 commits
  8. 08 Apr, 2010 1 commit
  9. 23 Mar, 2010 4 commits
  10. 11 Mar, 2010 1 commit
  11. 10 Mar, 2010 1 commit
  12. 08 Mar, 2010 2 commits
    • Michal Marek's avatar
      Revert "kbuild: specify absolute paths for cscope" · e93bc1a0
      Michal Marek authored
      This reverts commit eb8f844c. Ian
      Campbell writes:
      > I keep my kernel source tree on a more powerful build box where I run my
      > builds etc (including "make cscope") but run my editor from my
      > workstation with an NFS mount to the source. This worked fine for me
      > using relative paths for cscope. Using absolute paths in cscope breaks
      > this previously working setup because the root path is not the same on
      > both systems. I guess this is similar to moving the source tree around.
      >
      > Without wanting to start a flamewar it really sounds to me like we are
      > working around a vim (or cscope) bug here, emacs with cscope bindings
      > works fine in this configuration.
      
      Given that absolute paths can be forced by make O=. cscope, change the
      default back to relative paths.
      
      Ian Campbell <ijc@hellion.org.uk>
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      e93bc1a0
    • Michal Marek's avatar
      kbuild: Do not unnecessarily regenerate modules.builtin · a6c36632
      Michal Marek authored
      Only regenerate it if the configuration has changed. Also, do this after
      the modules build to fix errors with some weird Makefiles that are
      generated during build.
      Reported-by: default avatarEric Miao <eric.y.miao@gmail.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      a6c36632
  13. 07 Mar, 2010 9 commits
  14. 03 Mar, 2010 9 commits