Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
R
riscv-gcc-1
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
riscv-gcc-1
Commits
de43c613
Commit
de43c613
authored
Jan 04, 2007
by
Brooks Moses
Committed by
Brooks Moses
Jan 03, 2007
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* gfortran.texi (GNU Fortran and GCC): Rewrite
From-SVN: r120428
parent
e6b38f67
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
33 additions
and
43 deletions
+33
-43
gcc/fortran/ChangeLog
+4
-0
gcc/fortran/gfortran.texi
+29
-43
No files found.
gcc/fortran/ChangeLog
View file @
de43c613
2007-01-03 Brooks Moses <brooks.moses@codesourcery.com>
* gfortran.texi (GNU Fortran and GCC): Rewrite
2007-01-03 Brooks Moses <brooks.moses@codesourcery.com>
* gfortran.texi (Introduction): Lower "Part I:
Introduction" to a chapter, renumber Parts II and III to
Parts I and II.
...
...
gcc/fortran/gfortran.texi
View file @
de43c613
...
...
@@ -351,49 +351,35 @@ programs will call it for you.
@node
GNU
Fortran
and
GCC
@section
GNU
Fortran
and
GCC
@cindex
GNU
Compiler
Collection
GCC
used
to
be
the
GNU
``
C
''
Compiler
,
but
is
now
known
as
the
@dfn
{
GNU
Compiler
Collection
}.
GCC
provides
the
GNU
system
with
a
very
versatile
compiler
middle
end
(
shared
optimization
passes
),
and
back
ends
(
code
generators
)
for
many
different
computer
architectures
and
operating
systems
.
The
code
of
the
middle
end
and
back
end
are
shared
by
all
compiler
front
ends
that
are
in
the
GNU
Compiler
Collection
.
A
GCC
front
end
is
essentially
a
source
code
parser
and
an
intermediate
code
generator
.
The
code
generator
translates
the
semantics
of
the
source
code
into
a
language
independent
form
called
@dfn
{
GENERIC
}.
The
parser
takes
a
source
file
written
in
a
particular
computer
language
,
reads
and
parses
it
,
and
tries
to
make
sure
that
the
source
code
conforms
to
the
language
rules
.
Once
the
correctness
of
a
program
has
been
established
,
the
compiler
will
build
a
data
structure
known
as
the
@dfn
{
Abstract
Syntax
tree
},
or
just
@dfn
{
AST
}
or
``
tree
''
for
short
.
This
data
structure
represents
the
whole
program
or
a
subroutine
or
a
function
.
The
``
tree
''
is
passed
to
the
GCC
middle
end
,
which
will
perform
optimization
passes
on
it
.
The
optimized
AST
is
then
handed
off
too
the
back
end
which
assembles
the
program
unit
.
Different
phases
in
this
translation
process
can
be
,
and
in
fact
@emph
{
are
}
merged
in
many
compiler
front
ends
.
GNU
Fortran
has
a
strict
separation
between
the
parser
and
code
generator
.
The
goal
of
the
GNU
Fortran
project
is
to
build
a
new
front
end
for
GCC
.
Specifically
,
a
Fortran
95
front
end
.
In
a
non
-
@command
{
gfortran
}
installation
,
@command
{
gcc
}
will
not
be
able
to
compile
Fortran
source
code
(
only
the
``
C
''
front
end
has
to
be
compiled
if
you
want
to
build
GCC
,
all
other
languages
are
optional
).
If
you
build
GCC
with
@command
{
gfortran
},
@command
{
gcc
}
will
recognize
@file
{.
f
/
.
f90
/
.
f95
}
source
files
and
accepts
Fortran
specific
command
line
options
.
@cindex
GCC
GNU
Fortran
is
a
part
of
GCC
,
the
@dfn
{
GNU
Compiler
Collection
}.
GCC
consists
of
a
collection
of
front
ends
for
various
languages
,
which
translate
the
source
code
into
a
language
-
independent
form
called
@dfn
{
GENERIC
}.
This
is
then
processed
by
a
common
middle
end
which
provides
optimization
,
and
then
passed
to
one
of
a
collection
of
back
ends
which
generate
code
for
different
computer
architectures
and
operating
systems
.
Functionally
,
this
is
implemented
with
a
driver
program
(
@command
{
gcc
})
which
provides
the
command
-
line
interface
for
the
compiler
.
It
calls
the
relevant
compiler
front
-
end
program
(
e
.
g
.,
@command
{
f951
}
for
Fortran
)
for
each
file
in
the
source
code
,
and
then
calls
the
assembler
and
linker
as
appropriate
to
produce
the
compiled
output
.
In
a
copy
of
GCC
which
has
been
compiled
with
Fortran
language
support
enabled
,
@command
{
gcc
}
will
recognize
files
with
@file
{.
f
},
@file
{.
f90
},
and
@file
{.
f95
}
extensions
as
Fortran
source
code
,
and
compile
it
accordingly
.
A
@command
{
gfortran
}
driver
program
is
also
provided
,
which
is
identical
to
@command
{
gcc
}
except
that
it
automatically
links
the
Fortran
runtime
libraries
into
the
compiled
program
.
This
manual
specifically
documents
the
Fortran
front
end
,
which
handles
the
programming
language
'
s
syntax
and
semantics
.
The
aspects
of
GCC
which
relate
to
the
optimization
passes
and
the
back
-
end
code
generation
are
documented
in
the
GCC
manual
;
see
@ref
{
Top
,,
Introduction
,
gcc
,
Using
the
GNU
Compiler
Collection
(
GCC
)}.
The
two
manuals
together
provide
a
complete
reference
for
the
GNU
Fortran
compiler
.
@c
---------------------------------------------------------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment