Find a file
Neil Roberts 7333112ed0 i965: Fix output register sizes when variable ranges are interleaved
In 6f5abf3146 this code was fixed to calculate the maximum size of
an attribute in a seperate pass and then allocate the registers to
that size. However this wasn’t taking into account ranges that overlap
but don’t have the same starting location. For example:

layout(location = 0, component = 0) out float a[4];
layout(location = 2, component = 1) out float b[4];

Previously, if ‘a’ was processed first then it would allocate a
register of size 4 for location 0 and it wouldn’t allocate another
register for location 2 because it would already be covered by the
range of 0. Then if something tries to write to b[2] it would try to
write past the end of the register allocated for ‘a’ and it would hit
an assert.

This patch changes it to scan for any overlapping ranges that start
within each range to calculate the maximum extent and allocate that
instead.

Fixed Piglit’s arb_enhanced_layouts/execution/component-layout/
vs-fs-array-interleave-range.shader_test

Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com>
Fixes: 6f5abf3146 "i965: Fix output register sizes when multiple variables
       share a slot."
(cherry picked from commit 2d5ddbe960)
2018-07-05 10:00:13 -07:00
bin cherry-ignore: add a2f5292c82 2018-06-27 08:31:24 -07:00
build-support
docs docs: Add SHA256 sums to notes for 18.1.3 2018-06-29 11:00:48 -07:00
doxygen
include radeonsi: add support for VegaM 2018-04-18 14:45:33 -04:00
m4
scons meson/configure: detect endian.h instead of trying to guess when it's available 2018-03-23 11:44:21 +00:00
scripts
src i965: Fix output register sizes when variable ranges are interleaved 2018-07-05 10:00:13 -07:00
.dir-locals.el
.editorconfig
.gitattributes
.gitignore
.mailmap mailmap: Use Eric Engestrom's personal email address 2018-03-15 12:03:41 +00:00
.travis.yml travis: update libva required version 2018-04-27 10:11:58 -07:00
Android.common.mk meson/configure: detect endian.h instead of trying to guess when it's available 2018-03-23 11:44:21 +00:00
Android.mk
appveyor.yml
autogen.sh
CleanSpec.mk
common.py
configure.ac configure: use compliant grep regex checks 2018-06-21 08:12:39 -07:00
install-gallium-links.mk
install-lib-links.mk
Makefile.am autotools: include include/vulkan headers 2018-04-20 20:26:49 -07:00
meson.build meson: Correct behavior of vdpau=auto 2018-06-25 08:43:39 -07:00
meson_options.txt meson: Re-add auto option for omx 2018-03-07 13:30:53 -08:00
REVIEWERS
SConstruct
VERSION VERSION: bump version to 18.1.3 2018-06-29 10:29:48 -07:00

File: docs/README.WIN32

Last updated: 21 June 2013


Quick Start
----- -----

Windows drivers are build with SCons.  Makefiles or Visual Studio projects are
no longer shipped or supported.

Run

  scons libgl-gdi

to build gallium based GDI driver.

This will work both with MSVS or Mingw.


Windows Drivers
------- -------

At this time, only the gallium GDI driver is known to work.

Source code also exists in the tree for other drivers in
src/mesa/drivers/windows, but the status of this code is unknown.

Recipe
------

Building on windows requires several open-source packages. These are
steps that work as of this writing.

- install python 2.7
- install scons (latest)
- install mingw, flex, and bison
- install pywin32 from here: http://www.lfd.uci.edu/~gohlke/pythonlibs
  get pywin32-218.4.win-amd64-py2.7.exe
- install git
- download mesa from git
  see https://www.mesa3d.org/repository.html
- run scons

General
-------

After building, you can copy the above DLL files to a place in your
PATH such as $SystemRoot/SYSTEM32.  If you don't like putting things
in a system directory, place them in the same directory as the
executable(s).  Be careful about accidentially overwriting files of
the same name in the SYSTEM32 directory.

The DLL files are built so that the external entry points use the
stdcall calling convention.

Static LIB files are not built.  The LIB files that are built with are
the linker import files associated with the DLL files.

The si-glu sources are used to build the GLU libs.  This was done
mainly to get the better tessellator code.

If you have a Windows-related build problem or question, please post
to the mesa-dev or mesa-users list.