This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Question about organization of gfortran source code
- From: L R <grabmylongswordho at yahoo dot com>
- To: fortran at gcc dot gnu dot org
- Date: Mon, 8 Sep 2008 14:26:43 -0700 (PDT)
- Subject: Question about organization of gfortran source code
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=T4HfcicwixulF+bZGuJjTMVJ3J3PKF1qf6lMvXMqysiptp9beebrevY6sXQ0IG3n7OR8BsgmsyrUQWYobb4lXuwBXhNg9ZX7OasVkwNJm1kAyoaTsjkHXbfE5eh+jd2qTnVLs33YhOdCH3pYT7yapB7XGmZd+L0ERSLyzqebxSY=;
Hi, I am a high school student working on a project involving fortran.
Since I am focusing more on the optimization side of a compiler, I do
not want to spend ages writing a parser that will work for all of
fortran's weird gotcha's. I am trying to figure out from the sources
where the parser ends and the rest of it begins, but I am having a
little trouble understanding everything without reading 80% of the
code. Could someone please provide some insight into how the sources
are organized. I realize parse.c obviously deals with a lot of the
parsing, but I still am having trouble figuring out the execution flow.
Could someone please tell which sections of the program first deal with
the tokenization of raw strings all the way to when the program is
finally in the form of an expression tree. Thanks a lot!