-Mark the document OpenGL Insights chapter on ANGLE as historical
reference.
-Modify the visual studio build instruction in ANGLE'S orientation link.
-Point the Start Projects link to the angle starter bug lists.
-Remove doc/Starter-Projects.md.
 (most bugs listed in Starter-Projects.md are closed.
  mark bugs 2734, 2556, 2506 as starter bugs.
  remove link to WebGL conformance on Windows as they are outdated)
-Remove IRC channel join info.
-Add more instructions on how to join Angle Slack channel.
-Add warning indicating the iframe tags are not displayed properly in
doc/dEQP-Charts.md.

Bug: angleproject:6509
Change-Id: Idd4364fe48b506b44d3a2b40fa0e6ebd9e810a1b
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/3204132
Commit-Queue: Yuxin Hu <yuxinhu@google.com>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
This commit is contained in:
YuxinHu 2021-10-04 23:57:15 +00:00 коммит произвёл Angle LUCI CQ
Родитель d4c7b5946a
Коммит bf74475217
4 изменённых файлов: 13 добавлений и 117 удалений

Просмотреть файл

@ -64,8 +64,11 @@ View the [Dev setup instructions](doc/DevSetup.md).
## Contributing
* Join our [Google group](https://groups.google.com/group/angleproject) to keep up to date.
* Join us on IRC in the #ANGLEproject channel on FreeNode.
* Join us on [Slack](https://chromium.slack.com) in the #angle channel.
* Join us on [Slack](https://chromium.slack.com) in the #angle channel. You can
follow the instructions on the [choromium developer page](https://www.chromium.org/developers/slack)
for the steps to join the Slack channel. For Googlers, please follow the
instructions on this [document](https://docs.google.com/document/d/1wWmRm-heDDBIkNJnureDiRO7kqcRouY2lSXlO6N2z6M/edit?usp=sharing)
to use your google or chromium email to join the Slack channel.
* [File bugs](http://anglebug.com/new) in the [issue tracker](https://bugs.chromium.org/p/angleproject/issues/list) (preferably with an isolated test-case).
* [Choose an ANGLE branch](doc/ChoosingANGLEBranch.md) to track in your own project.
@ -77,11 +80,11 @@ View the [Dev setup instructions](doc/DevSetup.md).
* Use ANGLE's [coding standard](doc/CodingStandard.md).
* Learn how to [build ANGLE for Chromium development](doc/BuildingAngleForChromiumDevelopment.md).
* Get help on [debugging ANGLE](doc/DebuggingTips.md).
* Go through [ANGLE's orientation](doc/Orientation.md) and sift through [starter projects](doc/Starter-Projects.md).
* Go through [ANGLE's orientation](doc/Orientation.md) and sift through [starter projects](https://bugs.chromium.org/p/angleproject/issues/list?q=Hotlist%3DStarterBug). If you decide to take on any task, write a comment so you can get in touch with us, and more importantly, set yourself as the "owner" of the bug. This avoids having multiple people accidentally working on the same issue.
* Read about WebGL on the [Khronos WebGL Wiki](http://khronos.org/webgl/wiki/Main_Page).
* Learn about implementation details in the [OpenGL Insights chapter on ANGLE](http://www.seas.upenn.edu/~pcozzi/OpenGLInsights/OpenGLInsights-ANGLE.pdf) and this [ANGLE presentation](https://drive.google.com/file/d/0Bw29oYeC09QbbHoxNE5EUFh0RGs/view?usp=sharing).
* Learn about the initial ANGLE implementation details in the [OpenGL Insights chapter on ANGLE](http://www.seas.upenn.edu/~pcozzi/OpenGLInsights/OpenGLInsights-ANGLE.pdf) (this is not the most up-to-date ANGLE implementation details, it is listed here for historical reference only) and this [ANGLE presentation](https://drive.google.com/file/d/0Bw29oYeC09QbbHoxNE5EUFh0RGs/view?usp=sharing).
* Learn about the past, present, and future of the ANGLE implementation in [this presentation](https://docs.google.com/presentation/d/1CucIsdGVDmdTWRUbg68IxLE5jXwCb2y1E9YVhQo0thg/pub?start=false&loop=false).
* Watch a [short presentation](https://youtu.be/QrIKdjmpmaA) on the Vulkan back-end.
* Track the [dEQP test conformance](doc/dEQP-Charts.md)

Просмотреть файл

@ -7,7 +7,7 @@ A basic guide to get up and running fixing bugs and performance issues in ANGLE.
### Windows
- Download and install
[Visual Studio 2017 Community](https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx).
[Visual Studio Community](https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx).
Installing takes some time.
- Take the time to register a Microsoft account, otherwise you'll get nagged to death.
@ -25,7 +25,7 @@ A basic guide to get up and running fixing bugs and performance issues in ANGLE.
[the ANGLE wiki](https://chromium.googlesource.com/angle/angle/+/main/doc/DevSetup.md#Development-setup-Getting-the-source)
to set up the ANGLE solution for the first time.
- The VS 2017 solution will be in `c:/src/angle/out/sln/ANGLE.sln`. Open and let the installation
- If you follow the [ANGLE wiki VS solution building and debugging guide](https://chromium.googlesource.com/angle/angle/+/main/doc/DevSetup.md#building-and-debugging-with-visual-studio), the VS solution will be in `c:/src/angle/out/Debug/angle-debug.sln`. Open and let the installation
finish. **Important**: set indent style to spaces, not tabs!
- Building should work at this point!

Просмотреть файл

@ -1,111 +0,0 @@
# ANGLE Starter Projects
For the most up-to-date list of starter projects, see
[anglebug.com](https://bugs.chromium.org/p/angleproject/issues/list?q=Hotlist%3DStarterBug). If you
decide to take on any task, write a comment so you can get in touch with us, and more importantly,
set yourself as the "owner" of the bug. This avoids having multiple people accidentally working on
the same issue.
## Refactors
### EGL Validation Refactoring
[anglebug.com/798](http://anglebug.com/798)
Move all EGL validation into separate functions in ValidationEGL.h. This opens up many possibilities
for auto-generation of entry points and is simply a cleaner structure.
### EGL Entry Point Auto-generation
[anglebug.com/2621](http://anglebug.com/2621)
Auto-generate EGL entry points and stub functions. This greatly reduces the chance of bugs in this
highly repetitive code and reduces the friction to adding new extensions.
### Support Separate Read and Draw Surfaces
[anglebug.com/2620](http://anglebug.com/2620)
ANGLE has never supported binding separate read and draw surfaces with eglMakeCurrent due to its
architecture. Some refactoring could be done to support this use case.
### Convert GLenums into typed internal Enums
[anglebug.com/2169](http://anglebug.com/2169)
Using a compact enum instead of GLenum offers type safety. Flat enums can also index into flat
arrays. We are in the process of migrating all internal GLenums into packed enums.
## Medium Features
### Add an AST Validator to the Shader Translator
[anglebug.com/2733](http://anglebug.com/2733)
An AST validator will reduce the number of bugs in our AST transforms and allow us to be more
confident about all ASTs generated by the translator.
## Small Features
### Fix shader source viewing in RenderDoc/NSIGHT
[anglebug.com/2734](http://anglebug.com/2734)
It used to be possible to view the shader source when debugging shaders in graphics debuggers but
now only the shader disassembly is available.
### Implement Android CDD Extensions
[anglebug.com/2506](http://anglebug.com/2506)
The Android CDD requires some EGL and OpenGL ES extensions from every driver. Many of them are
simply exposing the native driver's extension to ANGLE's frontend.
## Performance
### Add perf test for eglMakeCurrent
[anglebug.com/2556](http://anglebug.com/2556)
Many customers switch Contexts frequently. MakeCurrent shows up as a hotspot. A performance test
would protect against regressions.
### Refactor std::maps into Static Arrays
[anglebug.com/1389](http://anglebug.com/1389)
ANGLE uses internal global maps for texture tables. We should rewrite them to save on binary size
and optimize startup time.
## Maintenance
### Add a presubmit python script
[anglebug.com/2626](http://anglebug.com/2626)
This simple script could verify that there is no diff on git cl upload. This saves developer time
in the long run.
## Conformance
### Vulkan ES2 fixes
[anglebug.com/2615](http://anglebug.com/2615) - see open blocking bugs. Also
[this link](https://bugs.chromium.org/p/angleproject/issues/list?can=2&q=Renderer%3DVulkan+-has%3Aowner&colspec=ID+Type+Status+Priority+Feature+Owner+Summary&cells=ids)
for open issues.
Many small edge cases still need attention.
### WebGL Conformance on Windows
[tracking document](https://docs.google.com/spreadsheets/d/1NQePFOdCKT1WKG2P4Qt8igLrLVy4U3vLOLvVWwbkllw/edit?usp=sharing)
ANGLE is preparing to release its OpenGL backend on Windows in Chrome using the passthrough command
decoder. There are still some failing WebGL tests.
### EGL Conformance
[anglebug.com/2623](http://anglebug.com/2623)
ANGLE's EGL implementation has a lot of holes in it's conformance. There are many tests that fail on
all platforms due to bugs in ANGLE's EGL frontend.

Просмотреть файл

@ -2,6 +2,10 @@
These charts are generated nightly from the [chrome GPU waterfall bots](https://ci.chromium.org/p/chromium/g/chromium.gpu.fyi/console?limit=200). The output of dEQP tests are parsed by [generate_stats.py](https://chromium.googlesource.com/angle/angle/+/HEAD/scripts/generate_stats.py) and collected into a Sheet here: https://docs.google.com/spreadsheets/d/1uttk1z8lJ4ZsUY7wMdFauMzUxb048nh5l52zdrAznek
Warning: the charts below that are wrapped by iframe tags may not display
properly on GitHub Markdown. The charts can be viewed best on the
[Chromium repo page](https://chromium.googlesource.com/angle/angle/+/HEAD/doc/dEQP-Charts.md).
[TOC]
## Win Desktop OpenGL Charts