| Age | Commit message (Collapse) | Author |
|---|
|
This has knock on effects in the store.
fix
|
|
It seems that we can end up with a null item in MuPDFReaderView
onSingleTap. Add some simple checks to avoid this.
|
|
Calculations that involved non power of 2 bpps were going wrong.
|
|
When blanking pixmaps (or converting pixmap colors), watch out for
integer overflows.
|
|
|
|
|
|
Omitting the unlisted UTF-8 and UTF-32 CMaps saves ~1M.
Omitting the unlisted other CMaps saves ~200k.
Define CJK_CMAPS=0 to skip all CMaps.
Define EXTRA_CMAPS=1 to include the various other CMaps.
Define UTF8_CMAPS=1 and UTF32_CMAPS to include the UTF-8 and UTF-32 CMaps.
|
|
Compile with -Os, -ffunction-sections, -fdata-sections and link
with --gc-sections and -s (strip) to include only the functions and
data tables actually required.
|
|
I had changed some code to *3 when creating the routine from the
4 bpp variant, but this particular multiplication should still
have been *4, as it was looking up in an int table.
|
|
In C we can't have a label as the only thing in a block.
|
|
Need to specify that we are using alphas now.
|
|
clang only accepts the unified format - so use the unified syntax
everywhere, and add .syntax unified to tell the gnu assembler we're
using the unified syntax.
|
|
Lab colorspaces had been broken due to incorrect clipping of
color values introduced in an effort to fix Bug 696796.
|
|
Just a few places in the MSVC projects didn't have this enabled.
|
|
Update the test device so it can be used 'wrapping' another
device.
In particular, it can be used to wrap the display list device
so that we can evaluate 'color or not' while building the
display list rather than having to rerun the display list
afterwards.
Also, give improved control over whether we test every pixel
of images/shadings.
|
|
memory.h isn't part of the C standard, and Xcode was getting upset
when building mupdf as a module:
error: include of non-modular header inside framework module
'MuPDF.mupdf.memento'
[-Werror,-Wnon-modular-include-in-framework-module]
|
|
|
|
We store an hb_font in every font, and currently have fz_drop_font
know to call harfbuzz to destroy it. This causes harfbuzz to be
included even in builds that never use it.
We improve this situation by storing both an hb_font, and a
function pointer to destroy it within fz_font. This costs us
an extra pointer per fz_font, but solves the problem.
|
|
This enables linker to drop .o files that aren't required.
|
|
Don't try to load SVG images if SVG support is disabled.
|
|
|
|
|
|
|
|
Introduce FZ_PLOTTER defines to set which defines we required.
Add FZ_ENABLE define to set which document handlers are built
by default.
|
|
|
|
|
|
Use do {} while(--w) rather than while(w--) {} as this safes a
test each time around the loop.
|
|
|
|
Again, mainly so profiling works nicely.
|
|
For the common cases, avoid the loop.
|
|
Profilers can't identify which of the switch arms we are in for
the inlined function calls, so rejig the code so that each of these
is a separate function.
In theory this code should be faster too, as the function 'lookup'
is only done one rather than once per line, but I don't expect this
to make a huge difference.
|
|
Use this for plotters so we can see which ones are being used
in any given build.
Build with -DTRACK_USAGE to enable.
|
|
|
|
|
|
PAM output was broken in the absence of alpha. Fixed now.
|
|
|
|
Converting a pixmap to an alpha only pixmap means "just keep
the alpha". If there IS no alpha, then a solid alpha is
assumed.
|
|
|
|
|
|
If we have alpha on the input, we preserve it. If we have no alpha
on the input, we have to create it in the output if the edges aren't
pixel aligned.
|
|
|
|
|
|
When no alpha present, we were omitting to decode the last
component.
|
|
In the absence of the source image having an alpha plane, we were
dropping the constant alpha during linear interpolated plotting.
|
|
Only do int to int copying if we have an int to copy from.
Also, when copying int to int, copy int32_t to int32_t to make
us more future proof.
|
|
|
|
|
|
|
|
Try and help C avoid pointer aliasing issues. Some of this may not
help at all. None of it should hurt though.
|
|
|
