BSD Commit Log Search

   HDL_G: Belatedly catch up with devmap change

   XXXTODO
   Stop using devmap for HDLG_IOW_VBASE and HDLG_80321_VBASE;
   let arm/xscale/i80321* codes use bus_space_handle_t instead of
   virtual address itself.

   tests/lib/libpthread/t_compat_cancel: Make linker warnings non-fatal.

   We will get warnings like:

   /home/riastradh/netbsd/current/src/tests/lib/libpthread/t_compat_cancel.c:233: warning: warning: reference to compatibility sigsuspend(); include <signal.h> for correct reference

   This is intended -- t_compat_cancel deliberately uses the compat
   symbols, not the modern symbols, in order to test the compat symbols.

   Fixes clang build because bsd.sys.mk enables -Wl,--fatal-warnings in
   LDFLAGS by default.

   PR lib/59240: POSIX.1-2024: cancellation point audit
   PR lib/59247: pthread_cancelstub.c is inadequately tested

   Enable setting of font variable on console and constty

   PR bin/59232

   logread: Use ulmin(9) for long v.s. size_t comparison

   instead of uimin(9).

   No real harm is expected IIUC.

   logread: Drop unnecessary (int) cast for uiomove(9)'s count

   which was changed to size_t back to 2002!
   https://cvsweb.netbsd.org/bsdweb.cgi/src/sys/sys/systm.h#rev1.149

   No practical problem is expected although.

   tests/lib/libc/gen/t_sleep: Sprinkle a few more diagnostics.

   PR misc/59254: tests/lib/libc/gen/t_sleep:kevent: intermittent failures

   t_fpclassify: Fix build on vax after #if'ing out subnormal tests.

   Must've neglected to compile-test this _on vax_, oops.

   PR port-vax/59261: t_fpclassify tests are failing

   make it clear that the # commands changes the number under the cursor

   s/scokets/sockets/ in comment.

   ia64: Include compat13 sigprocmask and sigsuspend stubs.

   All the other ports already do this.  Although ia64 was imported long
   after 1.4, the same is true of other ports that nevertheless include
   these stubs, like amd64.

   We could invent a new __NetBSD_Compat_Min__ macro like
   __NetBSD_Version__ that tells the earliest version of NetBSD for
   which we aim to support compat binaries, and use that to
   conditionalize tests like t_compat_cancel.c.  But that's a bit more
   trouble for something we can dispense with by a couple tiny syscall
   stubs.

   Should fix build for:

   PR lib/59240: POSIX.1-2024: cancellation point audit
   PR lib/59247: pthread_cancelstub.c is inadequately tested

   PR/59270: Taylor R Campbell: external/mit/isl: missing from doc/3RDPARTY

   evbarm/boards.plist: add marsboard

   libpthread: fix lint build

   lint: remove warning about 'constant in conditional context'

   This makes the '-X 161' option to lint invalid.

   Fix loading save files

   Both monster and weapon damage are represented as strings like "1d1", and
   internally the game keeps track of them as pointers to static strings
   in memory.  When saving, the game saves these pointers and when loading
   them the pointers end up being identical to before - which now points to
   undefined memory.

   So when loading a save game, reset the damage strings based on the type
   of monster or weapon.

   Pointed out and fix suggested by Anthony C Howe <achowe at snert.com>
   (committed with a small modification of said patch).

   wsmouse(4), wskbd(4): less DIAGNOSTIC, more KASSERT

   Also, add a DPRINTF to wsmouseclose() and wskbdclose(), mirroring their
   respective open functions.

   wsmux(4): fix open/close of child devices

   Only open child devices which aren't open already, and only close what
   we've opened. While here, fix all that #ifdef DIAGNOSTIC stuff. Most of
   that should just be KASSERTs.

   PR kern/59206

   uts(4): check uhidev_open() return before setting sc_enabled

   Also, check that sc_enabled is set before disabling.

   PR kern/59206

   tests/lib/libc/stdlib/t_strtod: Fix strtod_gherman_bug build on VAX.

   A typo (DBL_MANG_DIG) excluded this whole block, so my attempts to
   compile-test it failed to find the build errors.  Oops!

   PR port-vax/59264: t_strtod:strtod_gherman_bug test is failing

   tests/lib/libc/stdlib/t_strtod: Adapt strtod_gherman_bug to VAX.

   PR port-vax/59264: t_strtod:strtod_gherman_bug test is failing

   tests/lib/libc/gen/t_isnan: Fix architecture conditionals.

   1. Skip isinf_basic on VAX.  We have no other way to query `does this
      architecture support infinities?' and other tests already use
      isinf(HUGE_VAL) to determine that, so let's just make sure it
      works correctly on VAX.

   2. Don't skip these tests on m68k.  This was originally conditional
      on m68000 (which is to say, NetBSD's MACHINE_ARCH for Motorola
      68010 CPUs, i.e., the sun2 port), and was later mistakenly changed
      to m68k.  But there's no reason any m68k, 68010 or later, should
      skip this -- the floating-point format of the ABI does have NaN
      and infinity, whether it's a softfloat ABI or hardfloat ABI.

   PR misc/59266: t_isnan:isinf_basic test is bogus on some ports

   t___sync_lock: Try to make this work on VAX.

   Add note about why it _isn't_ also special on HPPA even though it may
   seems like it ought to be.

   PR port-vax/59260: t___sync_lock:__sync_lock_release_N tests are failing

   tests: Use `#if __*_HAS_DENORM__', not `#ifdef __*_HAS_DENORM__'.

   The compiler defines this to zero on, e.g., VAX.

   PR port-vax/59261: t_fpclassify tests are failing

   all: remove 'constant in conditional context' from LINTFLAGS

   Lint no longer emits this message, as it produced too many false
   positives.

   wskbd.9: fix function prototype

   sys/cdefs.h: remove lint CONSTCOND comment

   Since message 161 'constant in conditional context' has been removed,
   the comment is no longer needed.

   lint: remove warning about 'constant in conditional context'

   In a full NetBSD build, this warning occurs about 2400 times, making it
   the top 9 warning overall.  There is no evidence though that this
   warning detects any real bugs, so the noise it makes is not warranted.

   In this first step, the warning is still listed in the lint(7) manual
   page, as removing it from there would immediately make all places with
   "LINTFLAGS += -X 161" fail.  These '-X 161' flags cannot be removed
   first because then, the warning would step in and make the build fail.

   The next step is to clean up the "-X 161" options from all LINTFLAGS,
   and then the final step is to remove the warning from err.c.

   t_posix_fadvise: Don't check whether errno is preserved.

   I can find no guarantee in POSIX about posix_fadvise preserving
   errno; until such language is found I'm going to assume there is no
   such guarantee.

   What is happening is that, sometimes, rump_sys_posix_fadvise waits on
   a mutex or condvar, which uses _lwp_park internally, which sometimes
   wakes up early with EALREADY because a wakeup was already pending for
   the thread by the time it entered _lwp_park.  And that EALREADY is
   delivered by _lwp_park via errno.

   PR kern/53931: posix_fadvise_reg test case fails randomly on real
   hardware

   sys/ktrace.h: Need sys/param.h for MAXCOMLEN.

   Found while preparing to diagnose:

   PR kern/53931: posix_fadvise_reg test case fails randomly on real
   hardware

   Fix segfault when canceling "Quit" operation

   When pressing 'Q' followed by anything other than 'y', make sure not to
   end up calling __unreachable().

   Pointed out by Anthony C Howe <achowe at snert.com>