No description
Find a file
Caio Marcelo de Oliveira Filho ba1b41b504 glsl: do second pass of const propagation in loops
When handling loops in constant propagation, implement the "FINISHME"
comment like copy propagation: perform a first pass to find values
that can't be propagated, then perform a second pass with the ACP
containing still valid values.

Certain values are killed because the loop may run more than one
iteration, so we can't copy propagate them as they would be invalid in
the later iterations.

Reviewed-by: Eric Anholt <eric@anholt.net>
2018-07-16 16:33:39 -07:00
bin bin/get-pick-listh.sh: force git --pretty=medium 2018-05-23 09:54:17 -07:00
build-support
docs docs: Update news, calendar, and relnotes for 18.1.4 2018-07-13 13:54:46 -07:00
doxygen
include radeonsi: add support for Vega20 2018-07-12 16:48:12 -04:00
m4
scons mesa: Unconditionally enable floating-point textures 2018-06-18 09:29:38 +10:00
scripts
src glsl: do second pass of const propagation in loops 2018-07-16 16:33:39 -07:00
.dir-locals.el
.editorconfig
.gitattributes
.gitignore
.mailmap
.travis.yml travis: add libXrandr and its randrproto dependency 2018-06-21 11:46:47 +01:00
Android.common.mk android: enable VK_ANDROID_native_buffer 2018-05-21 09:26:50 +03:00
Android.mk
appveyor.yml appveyor: Consume LLVM 5.0.1. 2018-06-16 18:09:20 +01:00
autogen.sh
CleanSpec.mk
common.py
configure.ac util/set: add a basic unit test 2018-07-12 14:03:51 -07:00
install-gallium-links.mk
install-lib-links.mk
Makefile.am v3d: Switch the vc5 driver to using the finalized V3D UABI. 2018-05-16 21:19:07 +01:00
meson.build meson: Move xvmc test tools from unit tests to installed tools. 2018-07-13 13:29:29 -07:00
meson_options.txt meson: Move xvmc test tools from unit tests to installed tools. 2018-07-13 13:29:29 -07:00
README.rst README: wording fix for previous commit 2018-06-11 18:34:58 +01:00
REVIEWERS REVIEWERS: add root meson.build to the Meson reviewers group 2018-06-01 17:53:06 +01:00
SConstruct
VERSION Bump version after 18.1 2018-04-22 09:35:56 -07:00

`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library
======================================================


Source
------

This repository lives at https://gitlab.freedesktop.org/mesa/mesa.
Other repositories are likely forks, and code found there is not supported.


Build status
------------

Travis:

.. image:: https://travis-ci.org/mesa3d/mesa.svg?branch=master
    :target: https://travis-ci.org/mesa3d/mesa

Appveyor:

.. image:: https://img.shields.io/appveyor/ci/mesa3d/mesa.svg
    :target: https://ci.appveyor.com/project/mesa3d/mesa

Coverity:

.. image:: https://scan.coverity.com/projects/139/badge.svg?flat=1
    :target: https://scan.coverity.com/projects/mesa


Build & install
---------------

You can find more information in our documentation (`docs/install.html
<https://mesa3d.org/install.html>`_), but the recommended way is to use
Meson (`docs/meson.html <https://mesa3d.org/meson.html>`_):

.. code-block:: sh

  $ mkdir build
  $ cd build
  $ meson ..
  $ sudo ninja install


Support
-------

Many Mesa devs hang on IRC; if you're not sure which channel is
appropriate, you should ask your question on `Freenode's #dri-devel
<irc://chat.freenode.net#dri-devel>`_, someone will redirect you if
necessary.
Remember that not everyone is in the same timezone as you, so it might
take a while before someone qualified sees your question.
To figure out who you're talking to, or which nick to ping for your
question, check out `Who's Who on IRC
<https://dri.freedesktop.org/wiki/WhosWho/>`_.

The next best option is to ask your question in an email to the
mailing lists: `mesa-dev\@lists.freedesktop.org
<https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_


Bug reports
-----------

If you think something isn't working properly, please file a bug report
(`docs/bugs.html <https://mesa3d.org/bugs.html>`_).


Contributing
------------

Contributions are welcome, and step-by-step instructions can be found in our
documentation (`docs/submittingpatches.html
<https://mesa3d.org/submittingpatches.html>`_).

Note that Mesa uses email mailing-lists for patches submission, review and
discussions.