From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: <gcc@gcc.gnu.org>
Subject: [GCC Steering Committee] Android sub-port reviewer
Date: Thu, 29 Mar 2012 04:39:00 -0000 [thread overview]
Message-ID: <BCDE03C0-61B1-4C07-9E09-35A3E5C4BA38@codesourcery.com> (raw)
I volunteer as the reviewer for Android sub-port.
Android/Bionic support is an extension over Linux port and is being gradually added for more and more architectures. I wrote the original Android GCC support for ARM (under a watchful design eye of Joseph Myers), and know how the bits fit together.
As adding Android support to a new architecture requires changes to that architecture, the architecture maintainer will have the power of veto for the Android-related changes.
Thank you,
--
Maxim Kuvyrkov
CodeSourcery / Mentor Graphics
next reply other threads:[~2012-03-29 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 4:39 Maxim Kuvyrkov [this message]
2012-04-01 19:57 ` Maxim Kuvyrkov
2012-04-02 9:51 ` Jan Hubicka
2012-04-02 16:38 ` Richard Earnshaw
2012-04-02 18:45 ` Richard Sandiford
2012-04-02 20:55 ` Fu, Chao-Ying
2012-04-03 3:51 ` Andrew Pinski
2012-04-03 17:46 ` Fu, Chao-Ying
2012-04-03 18:08 ` Andrew Pinski
2012-04-03 18:28 ` Fu, Chao-Ying
2012-04-03 19:21 ` Maxim Kuvyrkov
2012-04-04 22:10 ` Fu, Chao-Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BCDE03C0-61B1-4C07-9E09-35A3E5C4BA38@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).