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
e75f4f15
Commit
e75f4f15
authored
Mar 17, 1999
by
Craig Burley
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update NEWS derived file
From-SVN: r25820
parent
f6a12244
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
gcc/f/NEWS
+4
-4
No files found.
gcc/f/NEWS
View file @
e75f4f15
...
...
@@ -66,7 +66,7 @@ about previous `g77' versions up-to-date.
the mainline, development version of `g77' within `egcs') is available
at `http://egcs.cygnus.com/onlinedocs/g77_news.html'.
The following information was last updated on 1999-03-1
3
:
The following information was last updated on 1999-03-1
7
:
In `egcs' 1.2 (versus 1.1.2):
=============================
...
...
@@ -105,9 +105,9 @@ In `egcs' 1.2 (versus 1.1.2):
In 0.5.24 and `egcs' 1.1.2 (versus 0.5.23 and 1.1.1):
=====================================================
* Fix the `IDate'
Intrinsic (VXT) so the returned year is in the
documented, non-Y2K-compliant range of 0-99, instead of being
returned as 100 in the year 2000.
* Fix the `IDate'
intrinsic (VXT) (in `libg2c') so the returned year
is in the documented, non-Y2K-compliant range of 0-99, instead of
being
returned as 100 in the year 2000.
* Fix the `Date_and_Time' intrinsic (in `libg2c') to return the
milliseconds value properly in VALUES(8).
...
...
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