Differences between revisions 41 and 42
Revision 41 as of 2011-04-18 15:37:01
Size: 962
Editor: 122
Comment:
Revision 42 as of 2011-04-18 15:46:49
Size: 4725
Editor: DiegoNovillo
Comment: Remove recent spam by Maya
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Denver Colorado - How to Find Luxury Hotels in Denver, Colorado == Welcome to the Getting Started section of the GCC Wiki ==
This section contains collected information geared towards folks who are new to GCC and may be feeling a bit lost in the barbaric jungles of GCC's source code. Although we are continuously trying to improve GCC's internal modularity and interfaces, the fact remains that GCC is about 20 years old, fairly large and we need to keep it working on the multitude of supported architectures and languages. So, getting to work with GCC can be a challenge.

Everyone is welcome to add links to tutorials, HOWTOs, cheat sheets, etc that may be floating around the net.
Line 4: Line 7:
If you are searching for the best luxury hotels in '''[[http://denvercolorado.org|denver colorado]]''', you do not have to worry because there are really a lot that you can just choose from in '''Colorado''' and you can really be sure with this. You will not be having a hard time in finding also because you can just see a lot of results in the web. You can really be sure that '''Denver''' is really one of the best vacation sites today that can just give you the best experience.
You can just go to '''[[http://denvercolorado.org|denver colorado]]''' if you really want to get the best vacation experience that you want to get in your vacation. You will never be having regrets in this and you can just be sure that '''co''' is really one of the best vacation sites where you can just enjoy today and you will never have to spend a lot if you will be going to '''Denver'''.
= Basics =
So, you are ready to contribute to GCC. We are constantly looking for new developers who are willing to donate their time to advance GCC.

Before you do, however, there is an important formality that you need to go through: '''Copyright assignment'''.

GCC is owned by the [[http://www.fsf.org|Free Software Foundation (FSF)]], as such, all contributors must assign their copyright to the FSF before any of their changes are accepted. The copyright assignment process is described in [[http://gcc.gnu.org/contribute.html|Contributing to GCC]]. (See also [[http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html|copyright papers]] and [[http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright|forms]].)

= Tutorials, HOWTOs =
 * [[http://www.cse.iitb.ac.in/grc/index.php?page=gcc-tut | Essential Abstractions in GCC (CGO 2011, Dr. Uday Khedker, Department of Computer Science & Eng IIT Bombay)]]
 * [[http://guerby.org/ftp/cfarm-ghm2010-20100725.pdf | GCC Compile Farm Lightning talk at GHM July 2010]]
 * [[http://blog.lxgcc.net/?page_id=116 | A blog about GCC development]]
 * [[http://www.seketeli.org/dodji/talks/eigen-2010/gcc-eigen-2010.pdf | G++ internals (Eigen Summit, Feb 2010)]]
 * [[http://guerby.org/ftp/gcc-toulibre-20091216.pdf | Overview of GCC for users, Toulibre Dec 2010]]
 * [[http://www.se-radio.net/podcast/2007-07/episode-61-internals-gcc |gcc internals podcast]] (Introduction)
 * [[http://www-ali.cs.umass.edu/~moss/610.html|CMP SCI 610/410 - Compiler Techniques - Fall 2008]] (multimedia lecture notes for a complete introductory compilers course with emphasis on gcc)
 * [[http://www.airs.com/dnovillo/200711-GCC-Internals|Updated GCC Internals Tutorial (November 2007)]]
 * [[OptimizationCourse|GCC Optimization Course and Tutorial]]
 * [[http://www.airs.com/dnovillo/Papers/#cgo2007|GCC Internals Tutorial at CGO 2007]]
 * [[http://www.cse.iitb.ac.in/~uday/gcc-workshop/?file=downloads|Workshop on GCC Internals (Advanced GCC Workshop 2007)]]
 * [[attachment:loopcheat.ps|Cheatsheet for loop optimizer (GCC summit 2007)]]
 * [[HomePage#summitprocs| GCC Summit Proceedings]]
 * [[http://www.cse.iitb.ac.in/grc/gccdocs.html| GCC Architecture Documents]] These documents by Abhijat Vichare are now a part of the [[http://www.cse.iitb.ac.in/grc|GCC Resource Center (GRC)]].
 * [[http://spindazzle.org/ggx/| The ggx patch archive]] Blog entries by Anthony Green illustrating design of an ISA while simultaneously implementing support for the new architecture in binutils and GCC
 * [[Dwarf2EHNewbiesHowto|Dwarf2 Exception Handler HOWTO]] Also known as the "EH newbies HOWTO".
 * [[http://www.cs.wustl.edu/~mdeters/seminar/fall2005/| gcc internals seminar notes]] (from 2005)
= Internal documentation =
 * [[http://gcc.gnu.org/onlinedocs/gccint/|GCC internals]]
 * [[http://gcc.gnu.org/onlinedocs/cppinternals/|CPP internals]]
 * /!\ [BROKEN] [[http://www.airs.com/dnovillo/gcc/doc/html|GCC Middle End and Back End API reference (automatically generated with doxygen every week)]]
= Dealing with the source code =
 * [[FormattingCodeForGCC|Formatting code for GCC]]
 * [[DebuggingGCC|Debugging GCC]]
 * [[Testing_GCC|Testing GCC]]
 * [[PerformanceTesting|Compile time and memory utilization testing]]
 * [[WritingANewPass|Writing a new pass]]
 * [[WritingANewFrontEnd|Writing a new front-end]]
 * [[WritingANewBackEnd|Writing a new back end]]
= Structure Of GCC =
 * [[StructureOfGCC|Structure of GCC]]
 * [[FrontEnd|Language front ends]]
 * [[MiddleEnd|Target independent code transformation frameworks]]
 * [[TreeOptimizers|Tree Optimizers]]
 * [[RTLOptimizers|RTL Optimizers]]
 * [[BackEnd|Target dependent passes and code generation]]
 * [[reload]]

== Reporting and correcting bugs ==

When using [[http://gcc.gnu.org/bugzilla|Bugzilla]], GCC maintainers (those having at least write after approval status to GCC trunk) [[http://gcc.gnu.org/ml/gcc/2009-10/msg00519.html|should preferably]] use their ''username''`@gcc.gnu.org` account to log in [[http://gcc.gnu.org/bugzilla|Bugzilla]].

Welcome to the Getting Started section of the GCC Wiki

This section contains collected information geared towards folks who are new to GCC and may be feeling a bit lost in the barbaric jungles of GCC's source code. Although we are continuously trying to improve GCC's internal modularity and interfaces, the fact remains that GCC is about 20 years old, fairly large and we need to keep it working on the multitude of supported architectures and languages. So, getting to work with GCC can be a challenge.

Everyone is welcome to add links to tutorials, HOWTOs, cheat sheets, etc that may be floating around the net.

Basics

So, you are ready to contribute to GCC. We are constantly looking for new developers who are willing to donate their time to advance GCC.

Before you do, however, there is an important formality that you need to go through: Copyright assignment.

GCC is owned by the Free Software Foundation (FSF), as such, all contributors must assign their copyright to the FSF before any of their changes are accepted. The copyright assignment process is described in Contributing to GCC. (See also copyright papers and forms.)

Tutorials, HOWTOs

Internal documentation

Dealing with the source code

Structure Of GCC

Reporting and correcting bugs

When using Bugzilla, GCC maintainers (those having at least write after approval status to GCC trunk) should preferably use their username@gcc.gnu.org account to log in Bugzilla.

None: GettingStarted (last edited 2018-05-15 21:37:44 by JonathanWakely)