1. 08 Feb, 2007 1 commit
  2. 07 Feb, 2007 1 commit
  3. 06 Feb, 2007 1 commit
  4. 10 Dec, 2006 1 commit
  5. 26 Sep, 2006 2 commits
    • Jan Beulich's avatar
      [PATCH] i386/x86-64: Work around gcc bug with noreturn functions in unwinder · adf14236
      Jan Beulich authored
      Current gcc generates calls not jumps to noreturn functions. When that happens the
      return address can point to the next function, which confuses the unwinder.
      
      This patch works around it by marking asynchronous exception
      frames in contrast normal call frames in the unwind information.  Then teach
      the unwinder to decode this.
      
      For normal call frames the unwinder now subtracts one from the address which avoids
      this problem.  The standard libgcc unwinder uses the same trick.
      
      It doesn't include adjustment of the printed address (i.e. for the original
      example, it'd still be kernel_math_error+0 that gets displayed, but the
      unwinder wouldn't get confused anymore.
      
      This only works with binutils 2.6.17+ and some versions of H.J.Lu's 2.6.16
      unfortunately because earlier binutils don't support .cfi_signal_frame
      
      [AK: added automatic detection of the new binutils and wrote description]
      Signed-off-by: default avatarJan Beulich <jbeulich@novell.com>
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      adf14236
    • Andi Kleen's avatar
      [PATCH] x86: Detect CFI support in the assembler at runtime · e2414910
      Andi Kleen authored
      ... instead of using a CONFIG option. The config option still controls
      if the resulting executable actually has unwind information.
      
      This is useful to prevent compilation errors when users select
      CONFIG_STACK_UNWIND on old binutils and also allows to use
      CFI in the future for non kernel debugging applications.
      
      Cc: jbeulich@novell.com
      Cc: sam@ravnborg.org
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      e2414910
  6. 25 Sep, 2006 2 commits
    • Sam Ravnborg's avatar
      kbuild: make V=2 tell why a target is rebuild · 45d506bd
      Sam Ravnborg authored
      tell why a a target got build
         enabled by make V=2
            Output (listed in the order they are checked):
               (1) - due to target is PHONY
               (2) - due to target missing
               (3) - due to: file1.h file2.h
               (4) - due to command line change
               (5) - due to missing .cmd file
               (6) - due to target not in $(targets)
      (1) We always build PHONY targets
      (2) No target, so we better build it
      (3) Prerequisite is newer than target
      (4) The command line stored in the file named dir/.target.cmd
          differed from actual command line. This happens when compiler
          options changes
      (5) No dir/.target.cmd file (used to store command line)
      (6) No dir/.target.cmd file and target not listed in $(targets)
          This is a good hint that there is a bug in the kbuild file
      
      This patch is inspired by a patch from: Milton Miller <miltonm@bga.com>
      
      Cc: Milton Miller <miltonm@bga.com>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      45d506bd
    • Sam Ravnborg's avatar
      kbuild: consistently decide when to rebuild a target · 48f1f058
      Sam Ravnborg authored
      Consistently decide when to rebuild a target across all of
      if_changed, if_changed_dep, if_changed_rule.
      PHONY targets are now treated alike (ignored) for all targets
      
      While add it make Kbuild.include almost readable by factoring out a few
      bits to some common variables and reuse this in Makefile.build.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      48f1f058
  7. 01 Aug, 2006 1 commit
  8. 31 Jul, 2006 1 commit
    • Roland McGrath's avatar
      [PATCH] vDSO hash-style fix · 0b0bf7a3
      Roland McGrath authored
      The latest toolchains can produce a new ELF section in DSOs and
      dynamically-linked executables.  The new section ".gnu.hash" replaces
      ".hash", and allows for more efficient runtime symbol lookups by the
      dynamic linker.  The new ld option --hash-style={sysv|gnu|both} controls
      whether to produce the old ".hash", the new ".gnu.hash", or both.  In some
      new systems such as Fedora Core 6, gcc by default passes --hash-style=gnu
      to the linker, so that a standard invocation of "gcc -shared" results in
      producing a DSO with only ".gnu.hash".  The new ".gnu.hash" sections need
      to be dealt with the same way as ".hash" sections in all respects; only the
      dynamic linker cares about their contents.  To work with older dynamic
      linkers (i.e.  preexisting releases of glibc), a binary must have the old
      ".hash" section.  The --hash-style=both option produces binaries that a new
      dynamic linker can use more efficiently, but an old dynamic linker can
      still handle.
      
      The new section runs afoul of the custom linker scripts used to build vDSO
      images for the kernel.  On ia64, the failure mode for this is a boot-time
      panic because the vDSO's PT_IA_64_UNWIND segment winds up ill-formed.
      
      This patch addresses the problem in two ways.
      
      First, it mentions ".gnu.hash" in all the linker scripts alongside ".hash".
       This produces correct vDSO images with --hash-style=sysv (or old tools),
      with --hash-style=gnu, or with --hash-style=both.
      
      Second, it passes the --hash-style=sysv option when building the vDSO
      images, so that ".gnu.hash" is not actually produced.  This is the most
      conservative choice for compatibility with any old userland.  There is some
      concern that some ancient glibc builds (though not any known old production
      system) might choke on --hash-style=both binaries.  The optimizations
      provided by the new style of hash section do not really matter for a DSO
      with a tiny number of symbols, as the vDSO has.  If someone wants to use
      =gnu or =both for their vDSO builds and worry less about that
      compatibility, just change the option and the linker script changes will
      make any choice work fine.
      Signed-off-by: default avatarRoland McGrath <roland@redhat.com>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Kyle McMartin <kyle@mcmartin.ca>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Jeff Dike <jdike@addtoit.com>
      Cc: Andi Kleen <ak@muc.de>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0b0bf7a3
  9. 01 Jul, 2006 1 commit
    • Sam Ravnborg's avatar
      kbuild: fix ia64 breakage after introducing make -rR · 5e8d780d
      Sam Ravnborg authored
      kbuild used $¤(*F to get filename of target without extension.
      This was used in several places all over kbuild, but introducing
      make -rR broke his for all cases where we specified full path to
      target/prerequsite. It is assumed that make -rR disables old style
      suffix-rules which is why is suddenly failed.
      
      ia64 was impacted by this change because several div* routines in
      arch/ia64/lib are build using explicit paths and then kbuild failed.
      
      Thanks to David Mosberger-Tang <David.Mosberger@acm.org> for an explanation
      what was the root-cause and for testing on ia64.
      
      This patch also fixes two uses of $(*F) in arch/um
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      5e8d780d
  10. 26 Jun, 2006 1 commit
    • Linus Torvalds's avatar
      Revert "kbuild: fix make -rR breakage" · d38b6968
      Linus Torvalds authored
      This reverts commit e5c44fd8.
      
      Thanks to Daniel Ritz and Michal Piotrowski for noticing the problem.
      
      Daniel says:
      
        "[The] reason is a recent change that made modules always shows as
         module.mod.  it breaks modprobe and probably many scripts..besides
         lsmod looking horrible
      
         stuff like this in modprobe.conf:
              install pcmcia_core /sbin/modprobe --ignore-install pcmcia_core; /sbin/modprobe pcmcia
         makes modprobe fork/exec endlessly calling itself...until oom
         interrupts it"
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      d38b6968
  11. 24 Jun, 2006 1 commit
    • Sam Ravnborg's avatar
      kbuild: fix make -rR breakage · e5c44fd8
      Sam Ravnborg authored
      make failed to supply the filename when using make -rR and using $(*F)
      to get target filename without extension.
      This bug was not reproduceable in small scale but using:
      $(basename $(notdir $@)) fixes it with same functionality.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      e5c44fd8
  12. 07 Apr, 2006 1 commit
  13. 05 Mar, 2006 1 commit
  14. 19 Feb, 2006 3 commits
  15. 06 Jan, 2006 1 commit
  16. 10 Sep, 2005 1 commit
  17. 25 Jul, 2005 1 commit
    • Sam Ravnborg's avatar
      kbuild: introduce Kbuild.include · 8ec4b4ff
      Sam Ravnborg authored
      Kbuild.include is a placeholder for definitions originally present in
      both the top-level Makefile and scripts/Makefile.build.
      There were a slight difference in the filechk definition, so the most videly
      used version was kept and usr/Makefile was adopted for this syntax.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      ---
      8ec4b4ff