Skip to content

A
angle
Switch branch/tag
  1. 21 Jul, 2016 4 commits
  3. 20 Jul, 2016 5 commits
  5. 19 Jul, 2016 10 commits
  7. 18 Jul, 2016 10 commits
  9. 16 Jul, 2016 1 commit
  11. 15 Jul, 2016 6 commits
  13. 14 Jul, 2016 4 commits
    • Stop linking a static_initializer into the Mac chromium build. · 313d9447
      Dirk Pranke authored 
      The :angle-image_util target was a source_set rather than a
static_library(), causing us to link in loadimage.cpp, which
pulled in mathutils.cpp, which contains a static initializer.
Switching :angle_image_util to a static library (which is what GYP
does) solved the problem.

R=rsesek@chromium.org, cwallez@chromium.org
BUG=628052

Change-Id: I63387b3fc9d799c92f7c1b49a1c7c7435e70a951
Reviewed-on: https://chromium-review.googlesource.com/360228Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: 's avatarRobert Sesek <rsesek@chromium.org>
Reviewed-by: 's avatarDirk Pranke <dpranke@chromium.org>
    • Pause TransformFeedback before eglMakeCurrent. · 4c32feb1
      Yuly Novikov authored 
      On Android Adreno eglMakeCurrent resets TransformFeedback position.
Workaround is to pause TransformFeedback before eglMakeCurrent
and resume afterwards.

BUG=angleproject:1426
TEST=TransformFeedbackTest.MultiContext

Change-Id: I4fdb9edbd28b4b16c01d1a94419e78160b31b79f
Reviewed-on: https://chromium-review.googlesource.com/355676Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
Reviewed-by: 's avatarGeoff Lang <geofflang@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
    • Compute row pitch using the size of the input pixel, not the format pixel. · 3f23406a
      Geoff Lang authored 
      For formats that can be loaded with data that has a different size pixel than
the internal format (UNSIGNED_INT -> GL_DEPTH_COMPONENT_24) the row length
would be computed as rowLength * 3 which is incorrect.

BUG=angleproject:1095

Change-Id: I0f60a3bb9bb387d475ddda1389a3b4b6f4973922
Reviewed-on: https://chromium-review.googlesource.com/360214Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>
    • Support precision emulation on HLSL · b741c761
      Olli Etuaho authored 
      Re-submit with missing virtual destructor and angle::NonCopyable
added.

Add precision emulation support to HLSL 4.1 output. This makes it
possible for developers to test their shaders for precision issues
easily on Chrome on Windows without having to use the GL backend. The
patch has been verified with Chrome on Windows to reproduce some
precision bugs in real-world WebGL content, including old versions of
the babylon.js library.

The EmulatePrecision AST transformation still relies on writing out
raw shader code for the rounding functions, with raw HLSL code added
alongside pre-existing GLSL and ESSL code. In some ways it would be
nicer to do the EmulatePrecision step as a pure AST transformation,
but on the other hand the raw code is much more readable and easier
to optimize.

To better support multiple output languages in EmulatePrecision, add a
RoundingHelperWriter class that has different subclasses for writing
the rounding functions in different languages.

The unit tests are expanded to cover the HLSL output of precision
emulation. The parts of the tests that require the HLSL output are
only active on Windows where ANGLE_ENABLE_HLSL define is added to the
unit tests. Putting the HLSL tests in an entirely separate file is a
worse alternative, since it would require either a lot of code
duplication or add a lot of boilerplate to the individual tests.

BUG=angleproject:1437
TEST=angle_unittests

Change-Id: I47d501037c206f4bd8b976d3acab9b21c717084c
Reviewed-on: https://chromium-review.googlesource.com/360152Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
Commit-Queue: Olli Etuaho <oetuaho@nvidia.com>