| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Update #3993.
|
|
|
|
|
|
|
| |
Ensure that the index is released before the structure containing it is
freed and NULLed.
Updates #4460
|
|
|
|
|
|
|
|
| |
The second allocation check was mistakenly rechecking the first
allocation. It now checks the correct allocation and ensures that names
is not NULL.
Updates #4462
|
| |
|
|
|
|
| |
Fix documentation.
|
|
|
|
|
| |
This function was declared, however, a definition was missing. Add a
validation test for it.
|
| |
|
|
|
|
|
|
|
|
| |
The Microchip PolarFire SoC support is implemented as a
riscv BSP variant to boot with any individual hart(cpu core)
or SMP based on the boot HARTID configurable and support
components are 4 CPU Cores (U54), Interrupt controller (PLIC),
Timer (CLINT), UART.
|
|
|
|
|
|
|
| |
Directly use "static inline" which is available in C99 and later. This brings
the RTEMS implementation closer to standard C.
Close #3935.
|
|
|
|
| |
Update #4702.
|
|
|
|
|
|
|
| |
All CPU ports used the same _CPU_Counter_difference() implementation. Remove
this CPU port interface and mandate a monotonically increasing CPU counter.
Close #3456.
|
|
|
|
|
|
|
|
| |
context after they are finialized after r336539, so do not do it.
Submitted by: David CARLIER <devnexen gmail com>
MFC after: 1 month (after r336539)
Differential Revision: https://reviews.freebsd.org/D16059
|
|
|
|
|
|
|
|
|
| |
copied_key and copied_salt are assigned with NULL and never used
otherwise. Remove the two variables and related code.
Reviewed by: pfg
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D16314
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using mis-identified many licenses so this was mostly a manual - error
prone - task.
The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mainly focus on files that use BSD 3-Clause license.
The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
Special thanks to Wind River for providing access to "The Duke of
Highlander" tool: an older (2014) run over FreeBSD tree was useful as a
starting point.
|
|
|
|
|
|
|
|
|
|
| |
and when doing it, consistently use explicit_bzero().
Update manual pages to match the behavior.
Reviewed by: pfg, allanjude, jmg
MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D16316
|
|
|
|
|
| |
Like SHA2-384:SHA2-512, SHA2-224 is simply a truncated SHA2-256 with a
different initial vector. Add to round out the complete basic SHA2 family.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
C99 allows array function parameters to use the static keyword for their
sizes. This tells the compiler that the parameter will have at least the
specified size, and calling code will fail to compile if that guarantee is
not met. However, this syntax is not legal in C++.
This commit reverts r300824, which worked around the problem for
sys/sys/md5.h only, and introduces a new macro: min_size(). min_size(x) can
be used in headers as a static array size, but will still compile in C++
mode.
Reviewed by: cem, ed
MFC after: 4 weeks
Sponsored by: Spectra Logic Corp
Differential Revision: https://reviews.freebsd.org/D8277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with more ILP and a preference for memory load instructions over large code
footprints with embedded immediate variables.
On amd64 CPUs from 2007-2008 there is not a significant change, but
amd64 CPUs from 2009-2010 get roughly 10% more throughput with this
code; amd64 CPUs from 2011-2012 get roughly 15% more throughput; and
AMD64 CPUs from 2013-2015 get 20-25% more throughput. The Raspberry
Pi 2 increases its throughput by 6-8%.
Sponsored by: Tarsnap Backup Inc.
Performance tested by: allanjude
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements SHA-512/256, which generates a 256 bit hash by
calculating the SHA-512 then truncating the result. A different initial
value is used, making the result different from the first 256 bits of
the SHA-512 of the same input. SHA-512 is ~50% faster than SHA-256 on
64bit platforms, so the result is a faster 256 bit hash.
The main goal of this implementation is to enable support for this
faster hashing algorithm in ZFS. The feature was introduced into ZFS
in r289422, but is disconnected because SHA-512/256 support was missing.
A further commit will enable it in ZFS.
This is the follow on to r292782
Reviewed by: cem
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D6061
|
|
|
|
|
|
|
|
|
|
|
| |
Use the C99 'static' keyword to hint to the compiler IVs and output digest
sizes. The keyword informs the compiler of the minimum valid size for a given
array. Obviously not every pointer can be validated (i.e., the compiler can
produce false negative but not false positive reports).
No functional change. No ABI change.
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cperciva's libmd implementation is 5-30% faster
The same was done for SHA256 previously in r263218
cperciva's implementation was lacking SHA-384 which I implemented, validated against OpenSSL and the NIST documentation
Extend sbin/md5 to create sha384(1)
Chase dependancies on sys/crypto/sha2/sha2.{c,h} and replace them with sha512{c.c,.h}
Reviewed by: cperciva, des, delphij
Approved by: secteam, bapt (mentor)
MFC after: 2 weeks
Sponsored by: ScaleEngine Inc.
Differential Revision: https://reviews.freebsd.org/D3929
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The VRSAVE feature of the Altivec unit can be used to reduce the amount of
Altivec registers which need to be saved/restored during interrupt processing
and context switches.
In order to use the VRSAVE optimization a corresponding multilib (-mvrsave) is
required, see GCC configuration. The -mvrsave option must be added to the
ABI_FLAGS of the BSP.
Currently only the -mcpu=e6500 based QorIQ BSP support this optimization.
Update #4712.
|
|
|
|
|
| |
Directly include <rtems/score/cpuopts.h> in header files using CPU build
options.
|
| |
|
|
|
|
| |
Closes #4713.
|
|
|
|
|
|
| |
Issue an error message if an SMP-specific scheduler is used and
RTEMS_SMP is disabled. This might be a more informative compared to
compiler or linker errors.
|
|
|
|
| |
Two interface specification items moved.
|
| |
|
| |
|
|
|
|
| |
Update #4691.
|
|
|
|
|
|
| |
Use RTEMS_ZERO_LENGTH_ARRAY for flexible array member.
Update #4662.
|
|
|
|
|
|
|
| |
It seems that recent GCC versions expect that functions with a "const type *"
parameter will read from the referenced location.
Update #4662.
|
|
|
|
| |
Updates #4691.
|
|
|
|
|
|
|
|
| |
The <rtems.h> header file should not unnecessarily include standard C
header files. The <string.h> and <limits.h> header includes were
removed in 2017.
Update #4662.
|
|
|
|
| |
Update #4706.
|
|
|
|
| |
Update #4706.
|
|
|
|
|
|
| |
This reverts commit f930206724e65f188fe3b095826ceb1b11000f65.
The linker set begin must be a symbol and not a zero-initialized item.
|
|
|
|
| |
- Stops the server crashing when setting breakpoints in .start
|
|
|
|
| |
UPdates #4706
|
|
|
|
| |
Updates #4706
|
|
|
|
|
|
|
|
| |
Added two pragmas to address, and changed the value of
AARCH64_EXCEPTION_MAKE_ENUM_64_BIT to INT_MAX because the old value was not
in range of an int.
Updates #4662
|
|
|
|
| |
Updates #4662
|
|
|
|
|
|
| |
Changed the size of the array to 1 to get rid of the warning.
Updates #4662
|
|
|
|
| |
Updates #4662
|
|
|
|
|
|
|
| |
The warning that this fixes states that "ISO C restricts enumerator values to
range of 'int'."
Updates #4662
|
|
|
|
|
|
|
| |
Changing the offset from 0 to 1 got rid of a warning stating that offset 0 is
out of bounds.
Updates #4662
|
|
|
|
| |
Updates #4662
|
| |
|
|
|
|
|
|
|
|
|
| |
This adds the configure option CONFIGURE_POSIX_TIMERS_FACE_BEHAVIOR
which allows the application to choose whether to have the POSIX
timer_create() function follow the behavior defined by POSIX or
the FACE Technical Standard.
Updates #4691.
|