Searched hist:1.1352 (Results 1 - 10 of 10) sorted by relevance

/src/sys/dev/pci/
H A Dpcidevs.h1.1352 Thu Feb 14 03:26:10 GMT 2019 msaitoh Regen.
H A Dpcidevs_data.h1.1352 Wed Feb 20 03:57:28 GMT 2019 msaitoh Regen.
H A Dpcidevs1.1352 Mon Nov 12 04:37:26 GMT 2018 msaitoh Add some Intel 100 series and C230 series devices.
/src/doc/
H A D3RDPARTY1.1352 Sat Aug 20 11:25:45 GMT 2016 christos unbound additions
H A DCHANGES1.1352 Sun Jan 31 21:02:05 GMT 2010 roy Import dhcpcd-5.1.5
/src/distrib/sets/lists/base/
H A Dmi1.1352 Sun Sep 08 22:35:02 GMT 2024 kre One more mozilla-rootcerts file that is now obsolete.
This fixes one current build breakage, but there is more to come.
/src/distrib/sets/lists/man/
H A Dmi1.1352 Sat Nov 05 09:22:43 GMT 2011 hannken Document virtio(4).
/src/distrib/sets/lists/tests/
H A Dmi1.1352 Sun Dec 22 23:25:14 GMT 2024 riastradh t_time_arith: New test for timer calculations.

This will facilitate fixing various problems in the arithmetic to
determine, given an itimer's scheduled time (it_value) and periodic
interval (it_interval) along with the current time of actual expiry
(now), what time the itimer should be rescheduled for (next, new
value of it_timer) on the same clock.

Later we can also put tests for other functions like tvtohz here, and
make them test many different values of hz/tick.

XXX Not 100% sure about all of these cases -- there is some room for
reasonable discussion about what the right answer is. But we have
unquestionably implemented the wrong thing for many of these cases,
even if the answers this test checks for may not be quite right yet.

PR kern/58922: itimer(9): arithmetic overflow
PR kern/58925: itimer(9) responds erratically to clock wound back
PR kern/58926: itimer(9) integer overflow in overrun counting
PR kern/58927: itimer(9): overrun accounting is broken
/src/share/mk/
H A Dbsd.own.mk1.1352 Tue Aug 08 06:27:32 GMT 2023 mrg introduce new GCC 12 warning disables and use them in a few places

this introduces 4 new warning disable flags:

CC_WNO_MISSING_TEMPLATE_KEYWORD
CC_WNO_REGISTER
CC_WNO_STRINGOP_OVERREAD
CC_WNO_ARRAY_BOUNDS

and documents them in README.warnings. of these, the string op
and array bounds are both problematic (real bugs) and also spurious
(not real bugs), and the other 2 are mostly temporary for older
3rd party code.

add some new uses of CC_WNO_STRINGOP_OVERFLOW.

fix m68k build for gallium and GCC 12.
/src/distrib/sets/lists/comp/
H A Dmi1.1352 Tue Dec 22 13:38:40 GMT 2009 jmmv Update file sets to match atf 0.7.

Completed in 948 milliseconds