Just IMHO;
It is probably too much trouble to pretend to add such checks
to the macros. People using them should know to avoid division
by zero and other issues that may happen.
Pedro.
On 04/26/16 14:59, Maxim Sobolev wrote:
Yeah, sure no rush. Another interesting mode of failure to check in
Author: ae
Date: Tue Apr 26 11:55:28 2016
New Revision: 298628
URL: https://svnweb.freebsd.org/changeset/base/298628
Log:
MFC r297820:
Fix the problem, when gpart(8) can't write both bootcode and partcode
in one command due to wrong file size limit. Do not use bootcode size
to
Author: pfg
Date: Tue Apr 26 17:39:54 2016
New Revision: 298653
URL: https://svnweb.freebsd.org/changeset/base/298653
Log:
MFC r298482:
Cleanup redundant parenthesis from existing howmany()/roundup() macro uses.
Requested by: dchagin
Modified:
stable/10/sys/amd64/amd64/pmap.c
Given the widespread use of those two macros, maybe we need howmany.9 and
roundup.9 manual pages with detailed formal description? Particularly
interested in how "return" supposed to be typed. Another thing is that
would be nice is some kind of automatic
#error/#warning/printf/KASSERT/panic when
Author: avg
Date: Tue Apr 26 07:40:07 2016
New Revision: 298621
URL: https://svnweb.freebsd.org/changeset/base/298621
Log:
MFC r297846: [amd64] dtrace_invop handler is to be called only for
kernel exceptions
Modified:
stable/10/sys/amd64/amd64/exception.S
Modified:
Author: avg
Date: Tue Apr 26 07:47:01 2016
New Revision: 298623
URL: https://svnweb.freebsd.org/changeset/base/298623
Log:
MFC r297846: [amd64] dtrace_invop handler is to be called only for
kernel exceptions
Fix up r298621.
Modified:
Directory Properties:
stable/10/ (props changed)