public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arpad Beszedes <beszedes@cc.u-szeged.hu>
To: gcc-help@gcc.gnu.org
Subject: How to contribute in the back end part
Date: Wed, 17 Apr 2002 01:59:00 -0000	[thread overview]
Message-ID: <3CBD36A1.1020409@cc.u-szeged.hu> (raw)

Hi all!

We would like to contribute to GCC by improving the ARM target 
(cross-compiler). This work would involve some code optimization and 
code generation issues. I would like to ask for a good starting point to 
do this job. We are completely new to GCC, so a tutorial-like document 
would be very useful. Is there any other document beside the "GCC 
internals", which could make us able to make useful contributions to 
GCC? (Or is it the source code the only "real documentation"?)

Thanks in advance,
   Arpad Beszedes.

-- 
******************************************************************
*  Arpad Beszedes - researcher                                   *
*                                                                *
*  Research Group on Artificial Intelligence - RGAI              *
*  Hungarian Academy of Sciences & University of Szeged, Hungary *
*  e-mail: beszedes@cc.u-szeged.hu                               *
*  web: http://www.inf.u-szeged.hu/~beszedes                     *
*  tel.: (+36) 62 544145                                         *
******************************************************************

             reply	other threads:[~2002-04-17  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17  1:59 Arpad Beszedes [this message]
     [not found] <616BE6A276E3714788D2AC35C40CD18D5B2776@whale.softwire.co.uk>
2002-04-17  2:37 ` Rupert Wood

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=3CBD36A1.1020409@cc.u-szeged.hu \
    --to=beszedes@cc.u-szeged.hu \
    --cc=gcc-help@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).