summaryrefslogtreecommitdiffstats
path: root/drivers/ieee1394/nodemgr.c
diff options
context:
space:
mode:
authorDavid Mosberger-Tang <davidm@hpl.hp.com>2005-05-04 06:42:00 -0700
committerTony Luck <tony.luck@intel.com>2005-05-10 13:52:00 -0700
commitbfd68594082d8384781c242aa72a7950b5cf51aa (patch)
tree00b5d0612bb155a83403580a4a88a0600c91e232 /drivers/ieee1394/nodemgr.c
parenta84f5770170232a48e753e02ee5f0f17ee17b791 (diff)
downloadblackbird-op-linux-bfd68594082d8384781c242aa72a7950b5cf51aa.tar.gz
blackbird-op-linux-bfd68594082d8384781c242aa72a7950b5cf51aa.zip
[IA64] Avoid .spillpsp directive in handcoded assembly
Some time ago, GAS was fixed to bring the .spillpsp directive in line with the Intel assembler manual (there was some disagreement as to whether or not there is a built-in 16-byte offset). Unfortunately, there are two places in the kernel where this directive is used in handwritten assembly files and those of course relied on the "buggy" behavior. As a result, when using a "fixed" assembler, the kernel picks up the UNaT bits from the wrong place (off by 16) and randomly sets NaT bits on the scratch registers. This can be noticed easily by looking at a coredump and finding various scratch registers with unexpected NaT values. The patch below fixes this by using the .spillsp directive instead, which works correctly no matter what assembler is in use. Signed-off-by: David Mosberger-Tang <davidm@hpl.hp.com> Signed-off-by: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'drivers/ieee1394/nodemgr.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud