+ Non-Algorithmic Maintainers
+
+loop optimizer Zdenek Dvorak dvorakz@suse.cz
+loop optimizer Daniel Berlin dberlin@dberlin.org
+middle-end Richard Guenther rguenther@suse.de
+libcpp Tom Tromey tromey@redhat.com
+blanket write Diego Novillo dnovillo@google.com
+blanket write Ian Lance Taylor ian@airs.com
+
+Note that individuals who maintain parts of the compiler as non-algorithmic
+maintainers need approval to check in algorithmic changes or changes
+outside of the parts of the compiler they maintain.
+
+ Reviewers
+
+dataflow Daniel Berlin dberlin@dberlin.org
+dataflow Paolo Bonzini bonzini@gnu.org
+dataflow Seongbae Park seongbae.park@gmail.com
+dataflow Kenneth Zadeck zadeck@naturalbridge.com
+Fortran Janne Blomqvist jb@gcc.gnu.org
+Fortran Tobias Burnus burnus@net-b.de
+Fortran François-Xavier Coudert fxcoudert@gcc.gnu.org
+Fortran Bud Davis jmdavis@link.com
+Fortran Jerry DeLisle jvdelisle@gcc.gnu.org
+Fortran Erik Edelmann erik.edelmann@iki.fi
+Fortran Steve Kargl sgk@troutmask.apl.washington.edu
+Fortran Thomas Koenig Thomas.Koenig@online.de
+Fortran Toon Moene toon@moene.indiv.nluug.nl
+Fortran Brooks Moses brooks.moses@codesourcery.com
+Fortran Tobias Schlüter tobias.schlueter@physik.uni-muenchen.de
+Fortran Paul Thomas pault@gcc.gnu.org
+
+
+Note that while reviewers can approve changes to parts of the compiler
+that they maintain, they still need approval for their own patches
+from other maintainers or reviewers.