This is the mail archive of the
mailing list for the GCC project.
Re: Hi! New to GCC
- From: Mikhail Maltsev <maltsevm at gmail dot com>
- To: Prasad Ghangal <prasad dot ghangal at gmail dot com>
- Cc: gcc at gcc dot gnu dot org, Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- Date: Sun, 24 Jan 2016 18:23:32 +0300
- Subject: Re: Hi! New to GCC
- Authentication-results: sourceware.org; auth=none
- References: <CAE+uiWYc3Gac1fJx+DGu-Mq8JnBqtFFE=_b=U6bxtjGN=QJ88w at mail dot gmail dot com> <56912D8E dot 2080001 at gmail dot com> <CAE+uiWYG+Mup3GRXTov5VwDEgag61yjGkJJf2PxEP2vLSKkghw at mail dot gmail dot com>
On 01/21/2016 09:06 AM, Prasad Ghangal wrote:
> Thanks Mikhail,
> As you have suggested I have built gcc on my laptop and gone through
> all the videos. The videos were very informative.
> Can I use any IDE for browsing gcc source code ?
Probably. Although IDE-s might have some performance and memory usage problems,
because GCC is a fairly large project. I used Netbeans some time ago and it
worked OK in most cases. Same caveats are:
1. Almost all source code is written in C++, even though files have extension
'.c'. You should configure your IDE appropriately.
2. During build GCC generates some source code in the build directory (like
gcc/insn-*.c files), so it is probably a good idea to include build directory in
If you decide to use a text editor like vim or emacs, there are some
configuration files which set proper source code formatting options, like
contrib/lvimrc. Settings for emacs are available here:
> Should I star looking at the "easy hacks" ?
Yes, probably it's a good point to start with.