is a best
practice even for single-processing. It's not a huge advantage, but it is
strictly better than having logically-const globals in the read/write data
segment.
On Thu, Jan 5, 2017 at 3:00 PM, Bruce Dawson <brucedaw...@google.com> wrote:
> The constant array xmlUnicodeBlocks is n
be applicable to
libxml2) is attached.
--
Bruce Dawson
commit eafa8bbee03e8ebba366be1fb8d5b1596a989a0a
Author: Bruce Dawson <brucedaw...@chromium.org>
Date: Thu Jan 5 11:25:58 2017 -0800
Add const in five places to move 1 KiB to .rdata
xmlUnicodeBlocks is logically
/
A similar fix upstream and perhaps a test of xmlUTF8Strsize()'s behavior
might be a good idea.
The bug does not occur when optimizing for speed.
FWIW.
--
Bruce Dawson
___
xml mailing list, project page http://xmlsoft.org/
xml@gnome.org
https://mail.gnome.org
wrote:
> On 07/03/2016 22:46, Bruce Dawson wrote:
>
>> The config.h file in win32\VC10 is incompatible with VS 2015 because VS
>> 2015
>> provides an implementation of snprintf and prohibits using the
>> preprocessor to
>> define it. Therefor an ifdef check is needed
le
> version rotting in multiple directories, unappealing indeed !
>
> > In any case, I think win32config.h should be updated; see below for my
> > responses to Bruce's comments about the differences between the configs.
>
> Sure, if people who are using the Windows platfo
lines:
#define SEND_ARG2_CAST
#define GETHOSTBYNAME_ARG_CAST
Which version should we prefer, and can we get the other version deleted
from libxml2 to avoid confusion?
--
Bruce Dawson
___
xml mailing list, project page http://xmlsoft.org/
xml@gnome.org
not define this in VS 2015 and above!
#define snprintf _snprintf
+#endif
#if _MSC_VER < 1500
#define vsnprintf(b,c,f,a) _vsnprintf(b,c,f,a)
#endif
It would be great to get that same patch in libxml2, and other developers
will need it if they use VC10\config.h.
--
Bruce
nk that the correct type would be ptrdiff_t, or size_t, or intptr_t,
or uintptr_t. I've attached the full set of warnings in case that is of any
assistance. Even though some of these warnings do not indicate actual bugs
it would still be best to use the correct type in order to avoid confusion
and war
is so high that the translation is
> not hurting. I have sites that literally exchange 1.5 million - 2.0
> million XML files per day (most in 10 hours) on a weenie little IBM using
> libxml2 to parse and create XML.
>
> My point on this is you may be able to fix by making it a 32 bit
&g
at 01:04:51PM -0800, Bruce Dawson wrote:
> > Resending now that I've joined the mailing list...
> >
> > While building 64-bit Chromium with VC++ 2015 Update 1 I noticed a
> > significant number of pointer truncation warnings in libxml, especially
> in
> > xpath.c. A
10 matches
Mail list logo
