ptid before invoking the suspend-all-but-this-thread logic. Otherwise,
when passed an LWP (as a result of 1.15 making LWPs the primary
identifier of live execution contexts), we try to suspend everything,
which goes poorly.
warn about the comparison always being true. Fixes build for macppc
target.
Problem noted by me, analysis and fix from Thomas Klausner.
Approved by wiz.
wrong registers with some opcodes, the error is:
Error: Illegal operands: There are only 32 single precision f registers; [0-31]
And the code to cause this is:
return (cond) ? x : -x;
where x is double.
AdminGroup
AdminOptions
that control who has the right to run cvs admin and cvs init.
For fine control over cvs commands, AdminOptions can be used.
I suggest AdminOptions=kmIqc
NetBSD options. Allows powerpc-*-netbsd* to accept "-R <arg>"
when <arg> doesn't exist in the host environment (as all other
NetBSD/ELF platforms do). As with MIPS and as before, accept
-G NUM, too.
The more portable way to pass arguments to the linker is, of course,
still -Wl,-R,/some/path (note that there are two commas).
anymore. Look in the ucontext_t for the next frame
instead. Backtrace through a signal handler invocation
works now.
(Since this change is NetBSD specific, this code shouldn't
be in a file which is shared among BSDs.)
* elf64-sparc.c (sparc64_elf_adjust_dynamic_symbol): When linking a
non-shared object, do not reserve space in .plt and .rela.plt for
regular symbols neither defined nor referenced in shared objects.
This fixes firefox for Havard
"tradlittlemips" and "tradbigmips" vectors.
The old vectors are meant for IRIX with it prelink shared library
support, and changes to better support this in binutils 2.15 broke
shared library support under NetBSD. The "trad" vectors are what 32bit
Linux and OpenBSD also use.
These vectors are also compatible with older NetBSD-built shared
libraries and programs so no flag day is necessary (Yay!).
These changes from Nick Hudson. Help also from Charles Hannum.
not if the 64 bit type is defined (BFD_HOST_64_BIT) because the second
is always defined, even if it falls back to a 32 bit type. In our case,
this was not the problem; the problem was that we bfd_vma is a 32 bit
type when BFD64 is not defined, so the shift was out of range.
