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
f4a7f981
Commit
f4a7f981
authored
Nov 20, 1998
by
Dave Love
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Regenerated.
From-SVN: r23734
parent
58dd1c34
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
13 deletions
+16
-13
gcc/f/BUGS
+16
-13
No files found.
gcc/f/BUGS
View file @
f4a7f981
...
@@ -44,6 +44,10 @@ port, build, and install `g77', *Note Problems Installing::.
...
@@ -44,6 +44,10 @@ port, build, and install `g77', *Note Problems Installing::.
Fixed in `egcs' version 1.1.
Fixed in `egcs' version 1.1.
* `g77' fails to warn about use of a "live" iterative-DO variable as
an implied-DO variable in a `WRITE' or `PRINT' statement (although
it does warn about this in a `READ' statement).
* A compiler crash, or apparently infinite run time, can result when
* A compiler crash, or apparently infinite run time, can result when
compiling complicated expressions involving `COMPLEX' arithmetic
compiling complicated expressions involving `COMPLEX' arithmetic
(especially multiplication).
(especially multiplication).
...
@@ -144,11 +148,12 @@ port, build, and install `g77', *Note Problems Installing::.
...
@@ -144,11 +148,12 @@ port, build, and install `g77', *Note Problems Installing::.
0.6 should solve most or all remaining problems (such as
0.6 should solve most or all remaining problems (such as
cross-compiling involving 64-bit machines).
cross-compiling involving 64-bit machines).
* Maintainers of gcc report that the back end definitely has "broken"
* Maintainers of `gcc' report that the back end definitely has
support for `COMPLEX' types. Based on their input, it seems many
"broken" support for `COMPLEX' types. Based on their input, it
of the problems affect only the more-general facilities for gcc's
seems many of the problems affect only the more-general facilities
`__complex__' type, such as `__complex__ int' (where the real and
for gcc's `__complex__' type, such as `__complex__ int' (where the
imaginary parts are integers) that GNU Fortran does not use.
real and imaginary parts are integers) that GNU Fortran does not
use.
Version 0.5.20 of `g77' works around this problem by not using the
Version 0.5.20 of `g77' works around this problem by not using the
back end's support for `COMPLEX'. The new option
back end's support for `COMPLEX'. The new option
...
@@ -156,15 +161,13 @@ port, build, and install `g77', *Note Problems Installing::.
...
@@ -156,15 +161,13 @@ port, build, and install `g77', *Note Problems Installing::.
the same "broken" mechanism as that used by versions of `g77'
the same "broken" mechanism as that used by versions of `g77'
prior to 0.5.20.
prior to 0.5.20.
* There seem to be some problems with passing constants, and perhaps
* `g77' sometimes produces invalid assembler code when using the
general expressions (other than simple variables/arrays), to
`-fPIC' option (such as compiling for ELF targets) on the Intel
procedures when compiling on some systems (such as i386) with
x86 architecture target. The symptom is that the assembler
`-fPIC', as in when compiling for ELF targets. The symptom is
complains about invalid opcodes. This bug is in the `gcc' back
that the assembler complains about invalid opcodes. This bug is
end.
in the gcc back end, and it apparently occurs only when compiling
sufficiently complicated functions *without* the `-O' option.
Fixed in `egcs' version 1.
1
.
Fixed in `egcs' version 1.
0.2
.
* `g77' currently inserts needless padding for things like `COMMON
* `g77' currently inserts needless padding for things like `COMMON
A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'
A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'
...
...
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