- Apr 07, 2019
-
-
Matt Turner authored
Signed-off-by: Matt Turner <mattst88@gmail.com>
-
Matt Turner authored
Signed-off-by: Matt Turner <mattst88@gmail.com>
-
- Mar 27, 2019
-
-
Signed-off-by: Matt Turner <mattst88@gmail.com>
-
When GNU Make is not from msys, the startup cost for sh.exe is massive compared to cmd.exe. Signed-off-by: Matt Turner <mattst88@gmail.com>
-
Signed-off-by: Matt Turner <mattst88@gmail.com>
-
Dylan Baker authored
This is unfortunately required to make the tests work correctly, as otherwise meson assumes that the files are C code not assembly. I've opened https://github.com/mesonbuild/meson/issues/5151, to discuss fixing the issue in meson upstream. Fixes #29
-
Dylan Baker authored
This simplifies the logic and fixes the loongson-mmi implementation to build correctly.
-
Dylan Baker authored
-
Dylan Baker authored
mentioned in #29
-
Dylan Baker authored
mach -> march
-
Dylan Baker authored
This issue causes openmp arguments to be injected into compilers that can support openmp, even if they don't. This issue will be fixed in 0.51 (code already landed in mesonbuild#5116), for older versions lets work around the issue.
-
- Feb 11, 2019
-
-
Maarten Lankhorst authored
And update RELEASING for the new meson build system. Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
-
Maarten Lankhorst authored
pixman-bits-image's wide helpers first obtains the 8-bits image, then converts it to float. This destroys all the precision that the wide path was offering. Fix this by making get_pixel() take a pointer instead of returning a value. Floating point will fill in a argb_t, while the 8-bits path will fill a 32-bits ARGB value. This also requires writing a floating point bilinear interpolator. With this change pixman can use the full floating point precision internally in all paths. Changes since v1: - Make accum and reduce an argument to convolution functions, to remove duplication. Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Acked-by: Basile Clement <basile-pixman@clement.pm>
-
Basile Clement authored
This patch modifies the gradient walker to be able to generate floating point values directly in addition to a8r8g8b8 32 bit values. This is then used by the various gradient implementations to render in floating point when asked to do so, instead of rendering to a8r8g8b8 and then expanding to floating point as they were doing previously. Changes since v1 (mlankhorst): - Implement pixman_gradient_walker_pixel_32 without calling pixman_gradient_walker_pixel_float, to prevent performance degradation. Suggested by Adam Jackson. - Fix whitespace errors. - Remove unnecessary function prototypes in pixman-private.h Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> [mlankhorst: Add comment about pixman_contract_from_float, based on Basille's suggestion] Acked-by: Basile Clement <basile-pixman@clement.pm>
-
- Jan 16, 2019
-
-
Reviewed-by: Matt Turner <mattst88@gmail.com>
-
Reviewed-by: Matt Turner <mattst88@gmail.com>
-
- Dec 07, 2018
-
-
Maarten Lankhorst authored
And bump meson version to 37.1 as well. Seems my push to upstream failed. Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
-
Maarten Lankhorst authored
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
-
- Nov 29, 2018
-
-
-
This commit adds a meson build system for pixman. It carries the usual improvements of meson, better clean build time, much better incremental build times, while being simpler and easier to understand. This takes advantage of some features from the most recent versions of meson: the builtin openmp dependency and the feature option type. There are a couple of things that I've done a bit differently than the autotools build system, I've built a libdemos which is the utilities from the demos folder, and I've linked the demos with libtestutils from tetsts, otherwise I expect that most things will be the same. I've tested so far cross compiling from x86_64 -> x86, x86_64 -> Aarch64, and Linux to Windows via mingw, as well as native x86_64 Linux builds which all work. I've also built with mingw nativly, there are some test failures there. An MSVC build can be generated, but fails. v2: - set WORDS_BIGENDIAN in the config for big endian systems.
-
This sets the style for meson (which uses the upstream style, 2 space indent with no tabs), and sets the tab_width to 8 per the CODING_STYLE document.
-
- Nov 21, 2018
-
-
Maarten Lankhorst authored
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
-
Maarten Lankhorst authored
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
-
- Nov 06, 2018
-
-
Maarten Lankhorst authored
Add some basic tests to ensure that the newly added formats work as intended. Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-
Maarten Lankhorst authored
Pixman is already using the floating point formats internally, expose this capability in case someone wants to support higher bit per component formats. This is useful for igt which depends on cairo to do the rendering. It can use it to convert floats internally to planar Y'CbCr formats, or to F16. We add a new type PIXMAN_TYPE_RGBA_FLOAT for this format, which is an all float array of R, G, B, and A. Formats that use mixed float/int RGBA aren't supported, and will probably need their own type. Changes since v1: - Use RGBA 128 bits and RGB 96 bits memory layouts, to better match the opengl format. Changes since v2: - Add asserts in accessor and for strides to force alignment. - Move test changes to their own commit. Changes since v3: - Define 32bpc as PIXMAN_FORMAT_PACKED_C32 - Rename pixman accessors from rgb*_float_float to rgb*f_float Changes since v4: - Create a new PIXMAN_FORMAT_BYTE for fitting up to 64 bits per component. (based on Siarhei Siamashka's suggestion) - Use new format type PIXMAN_TYPE_RGBA_FLOAT Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> #v4 [mlankhorst: Fix missing braces in PIXMAN_FORMAT_RESHIFT macro]
-
- Jul 06, 2018
-
-
Currently the number of bits per pixel is used instead of the number of bytes per pixel when calculating image strides. This does not cause any real problems, but the gaps between scanlines are excessively large. This patch actually converts bits to bytes and rounds up the result to the nearest byte boundary. Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com> Reviewed-by: <soren.sandmann@gmail.com>
-
- Jun 05, 2018
-
-
__builtin_shuffle was removed in clang 5.0. Build log says: test/utils-prng.c:207:27: error: use of unknown builtin '__builtin_shuffle' [-Wimplicit-function-declaration] randdata.vb = __builtin_shuffle (randdata.vb, bswap_shufflemask); ^ test/utils-prng.c:207:25: error: assigning to 'uint8x16' (vector of 16 'uint8_t' values) from incompatible type 'int' randdata.vb = __builtin_shuffle (randdata.vb, bswap_shufflemask); ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 errors generated Link to original discussion: http://lists.llvm.org/pipermail/cfe-dev/2017-August/055140.html It's possible to build pixman if attached patch is applied. Basically patch adds check for __builtin_shuffle support and in case there is none, falls back to clang-specific __builtin_shufflevector that do the same but have different API. Bugzilla: https://bugs.gentoo.org/646360 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104886 Tested-by: Philip Chimento <philip.chimento@gmail.com> Reviewed-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Adam Jackson <ajax@redhat.com>
-
Adam Jackson authored
ci: Add .gitlab-ci.yml See merge request pixman/pixman!1
-
Adam Jackson authored
Just builds on Fedora 28 for x86_64 at the moment, but it's a start. Credit to Daniel Stone for eliminating the nested docker image. Signed-off-by: Adam Jackson <ajax@redhat.com>
-
- May 14, 2018
-
-
Use vector intrinsic for loading possibly unaligned data instead of a typecast. Bugzilla: https://bugzilla.redhat.com/1572540 Signed-off-by: Dan Horák <dan@danny.cz> Signed-off-by: Adam Jackson <ajax@redhat.com> Tested-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
-
- Jan 09, 2018
-
-
Behdad Esfahbod authored
...to avoid default promotion to signed int, which causes undefined behaviour in the shift expression.
-
- Sep 03, 2016
-
-
Søren Sandmann authored
This reverts commit 375f5ec5. This patch was accidentally pushed.
-
Expanded the size slightly (from ~4.25 to 5) to make the cutoff less noticable. Previouly the value at the cutoff was gaussian_filter(sqrt(2)*3/2) = 0.00626 which is larger than the difference between 8-bit pixels (1/255 = 0.003921). New cutoff is gaussian_filter(2.5) = 0.001089 which is smaller. v11: added some math to commit message v14: left SIGMA in there Signed-off-by: Bill Spitzak <spitzak@gmail.com> Acked-by: Oded Gabbay <oded.gabbay@gmail.com> Reviewed-by: Søren Sandmann <soren.sandmann@gmail.com>
-
v11: Restored range checks Signed-off-by: Bill Spitzak <spitzak@gmail.com> Reviewed-by: Oded Gabbay <oded.gabbay@gmail.com>
-
Søren Sandmann authored
There are a few bugs in the current normalization code (1) The normalization is based on the sum of the *floating point* values generated by integral(). But in order to get the sum to be close to pixman_fixed_1, the sum of the rounded fixed point values should be used. (2) The multiplications in the normalization loops often round the same way, so the residual error can fairly large. (3) The residual error is added to the sample located at index (width - width / 2), which is not the midpoint for odd widths (and for width 1 is in fact outside the array). This patch fixes these issues by (1) using the sum of the fixed point values as the total to divide by, (2) doing error diffusion in the normalization loop, and (3) putting any residual error (which is now guaranteed to be less than pixman_fixed_e) at the first sample, which is the only one that didn't get any error diffused into it. Signed-off-by: Søren Sandmann <soren.sandmann@gmail.com>
-
- Sep 02, 2016
-
-
Søren Sandmann authored
The convolution of two BOX filters is simply the length of the interval where both are non-zero, so we can simply return width from the integral() function because the integration region has already been restricted to be such that both functions are non-zero on it. This is both faster and more accurate than doing numerical integration. This patch is based on one by Bill Spitzak https://lists.freedesktop.org/archives/pixman/2016-March/004446.html with these changes: - Rebased to not assume any changes in the arguments to integral(). - Dropped the multiplication by scale - Added more details in the commit message. Signed-off-by: Søren Sandmann <soren.sandmann@gmail.com> Reviewed-by: Bill Spitzak <spitzak@gmail.com>
-
Only the triangle is discontinuous at 0. The other filters resemble a cubic closely enough that Simpsons integration works without splitting. Changes by Søren: Rebase without the changes to the integral function, update comment to match the new code. Signed-off-by: Bill Spitzak <spitzak@gmail.com> Signed-off-by: Søren Sandmann <soren.sandmann@gmail.com> Reviewed-by: Søren Sandmann <soren.sandmann@gmail.com>
-
Simpsons uses cubic curve fitting, with 3 samples defining each cubic. This makes the weights of the samples be in a pattern of 1,4,2,4,2...4,1, and then dividing the result by 3. The previous code was using weights of 1,2,0,6,0,6...,2,1. With this fix the integration is accurate enough that the number of samples could be reduced a lot. Multiples of 12 seem to work best. v7: Merged with patch to reduce from 128 samples to 16 v9: Changed samples from 16 to 12 v10: Fixed rebase error that made it not compile v11: minor whitespace change v14: more whitespace changes Signed-off-by: Bill Spitzak <spitzak@gmail.com> Reviewed-by: Oded Gabbay <oded.gabbay@gmail.com> Reviewed-by: Søren Sandmann <soren.sandmann@gmail.com>
-
Rearranged so that the entire block of memory for the filter pair is allocated first, and then filled in. Previous version allocated and freed two temporary buffers for each filter and did an extra memcpy. v8: small refactor to remove the filter_width function v10: Restored filter_width function but with arguments changed to match later patches v11: Removed unused arg and pointer from filter_width function Whitespace fixes. Signed-off-by: Bill Spitzak <spitzak@gmail.com> Reviewed-by: Oded Gabbay <oded.gabbay@gmail.com> Acked-by: Søren Sandmann <soren.sandmann@gmail.com>
-
If enable-gnuplot is configured, then you can pipe the output of a pixman-using program to gnuplot and get a continuously-updated plot of the horizontal filter. This works well with demos/scale to test the filter generation. The plot is all the different subposition filters shuffled together. This is misleading in a few cases: IMPULSE.BOX - goes up and down as the subfilters have different numbers of non-zero samples IMPULSE.TRIANGLE - somewhat crooked for the same reason 1-wide filters - looks triangular, but a 1-wide box would be more accurate Changes by Søren: Rewrote the pixman-filter.c part to - make it generate correct coordinates - add a comment on how coordinates are generated - in rounding.txt, add a ceil() variant of the first-sample formula - make the gnuplot output slightly prettier v7: First time this ability was included v8: Use config option Moved code to the filter generator Modified scale demo to not call filter generator a second time. v10: Only print if successful generation of plots Use #ifdef, not #if v11: small whitespace fixes v12: output range from -width/2 to width/2 and include y==0, to avoid misleading plots for subsample_bits==0 and for box filters which may have no small values. Signed-off-by: Bill Spitzak <spitzak@gmail.com>
-