Remove the --silent argument from libtool so the build-log scanner does
complain about "compiler-flags-hidden 2"
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
tfm.h contains declarations for the public part of the library.
tfm_private.h contains the function which are private to tfm and should
not be exposed to the public.
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
This should enable 64bit math on 64bit architecures besides amd64 (like
ppc64, sparc64 and so on)
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To meet Debian's reproducible builds [0] goal I remove the __DATE__
macro.
In case this is not acceptable because the date of build is _really_
important / required I could come with a ifdef or something else.
[0] https://wiki.debian.org/ReproducibleBuilds
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
There is a bugzilla entry at clamav [0] reports a problem on s390x
"mul/fp_mul_comba_20.c:91: warning: right shift count >= width of type"
because fp_digit is 64bit and according to the comment it should be
smaller.
s390x is 64bit platform i.e. long and long long are both 64bit. The
same is true for ppc64, arm64 or sparc64 (RIP alpha).
The headerfile seems only to define FP_64BIT on x86_64.
The current code seems to define SIZEOF_FP_DIGIT either to 8 (64bit) or
to 4 in the else case and 4 looks like int and not long. Therefore the
change here.
If this change makes no sense and you would prefer to use something like
#if __SIZEOF_LONG__ == 8
#define FP_64BIT
#endif
to autodetect a 64bit platform then we could try do this instead. I
haven't tested this patch nor verified that the problem still occures.
If you have no obvious solution and would like to have a confirmation
that this patch solves a problem I could try to get my hands on
something not x86 with 64bit in order to verify.
[0] https://bugzilla.clamav.net/show_bug.cgi?id=9017
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
strncat' last argument is the remaining size of the buffer given in the
first argument, not the total buffer length.
Reported-by: contact@oppida.fr via clamav #11166
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
This was reported in clamav via a "coverity report" #11125/#11126. I can't
get the coverity report and I've been told that
|< linnatic> bigeasy: unfortunately, I can't get you the coverity report
|< linnatic> bigeasy: but it does seem that the patch is not
|required as the possible coverity issue is unlikely to occur
so if you thing that this patch is not required (which is what I assume) then
please drop that patch, I just added since it was in the clamav tree…
[sebastian@breakpoint: patch description]
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
If maxlen is too small then we get FP_OKAY as return value but not
everything is part of the string. This patch changes it so that the
caller learns about this short comming.
While at it, drop the doxygen style comment. It is the only of his kind
and does no longer match the code.
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Previous patch modified constraints from =m to =g. Turns out this also
allows registers which doesn't work with the inline assembly
instructions.
If we change back to =m GCC 5.0 warns that constraints do not allow a
register.
In order to work around these issues we now pass the arguments in
registers and let GCC handle the loading & storing.
It is not implemened yet, just added to the headerfile. Therefore I don't
think it is a ABI breakage if I change maxlen from int to unsigned int.
The function releases fp_toradix() for the work which in turn now calls
fp_toradix_n() with a largest possible maxlen parameter.
Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
