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
6a843296
Commit
6a843296
authored
May 06, 1999
by
Craig Burley
Committed by
Craig Burley
May 06, 1999
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc improvements
From-SVN: r26806
parent
52dff54a
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
26 additions
and
14 deletions
+26
-14
gcc/f/ChangeLog
+6
-0
gcc/f/g77.texi
+20
-14
No files found.
gcc/f/ChangeLog
View file @
6a843296
Thu May 6 12:40:21 1999 Craig Burley <craig@jcb-sc.com>
* g77.texi (Arbitrary Concatenation): Put this under
"Missing Features" instead of "Projects".
(Internals Documentation): Point to new "Front End" chapter.
Thu May 6 08:23:52 1999 Craig Burley <craig@jcb-sc.com>
* bugs.texi, news.texi: Automatic arrays reportedly working
...
...
gcc/f/g77.texi
View file @
6a843296
...
...
@@ -11389,6 +11389,7 @@ GNU Fortran language:
* Better Source Model::
* Fortran 90 Support::
* Intrinsics in PARAMETER Statements::
* Arbitrary Concatenation::
* SELECT CASE on CHARACTER Type::
* RECURSIVE Keyword::
* Popular Non-standard Types::
...
...
@@ -11529,6 +11530,22 @@ But, if the @code{gcc} back end is enhanced to provide
such a facility, @code{g77} will likely use that facility
in implementing this feature soon afterwards.
@node Arbitrary Concatenation
@subsection Arbitrary Concatenation
@cindex concatenation
@cindex CHARACTER*(*)
@cindex run-time, dynamic allocation
@code{g77} doesn't support arbitrary operands for concatenation
in contexts where run-time allocation is required.
For example:
@smallexample
SUBROUTINE X(A)
CHARACTER*(*) A
CALL FOO(A // 'suffix')
@end smallexample
@node SELECT CASE on CHARACTER Type
@subsection @code{SELECT CASE} on @code{CHARACTER} Type
...
...
@@ -14058,20 +14075,6 @@ sprinkled throughout.
It is not worth repeating them here.
@item
@cindex concatenation
@cindex CHARACTER*(*)
@cindex run-time, dynamic allocation
Support arbitrary operands for concatenation, even in contexts where
run-time allocation is required.
For example:
@smallexample
SUBROUTINE X(A)
CHARACTER*(*) A
CALL FOO(A // 'suffix')
@end smallexample
@item
Consider adding a @code{NUMERIC} type to designate typeless numeric constants,
named and unnamed.
The idea is to provide a forward-looking, effective
...
...
@@ -14176,6 +14179,9 @@ Better info on how @code{g77} works and how to port it is needed.
Much of this should be done only after the redesign planned for
0.6 is complete.
@xref{Front End}, which contains some information
on @code{g77} internals.
@node Internals Improvements
@section Internals Improvements
...
...
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