@@ -15,7 +15,7 @@ <h1>Hercules Release Notes and Known Issues</h1>
15
15
< a name =4.2 > </ a >
16
16
< hr noshade >
17
17
18
- < h2 > Release notes for SDL Hyperion 4.2 < small > (under development) </ small > </ h2 >
18
+ < h2 > Release notes for < a href =" https://github.com/ SDL-Hercules-390/hyperion/releases " > SDL Hyperion 4.2</ a > </ h2 >
19
19
< p >
20
20
< dl >
21
21
@@ -81,23 +81,22 @@ <h2>Release notes for SDL Hyperion 4.2 <small> (under development) </smal
81
81
</ p >
82
82
83
83
84
- < dt > Partial implementation of PFPO (Perform Floating Point Operation) instruction
84
+ < dt > PFPO (Perform Floating Point Operation) instruction
85
85
< dd >
86
86
< p >
87
- Thanks to a recent contribution by one of our users , Hercules now has a partial
87
+ Thanks to hard work of one of our developers , Hercules now has a < i > complete </ i >
88
88
implementation of the PFPO (Perform Floating Point Operation) instruction.
89
- (Previously we had no implementation at all.)
89
+ < i > (previously we had no implementation at all!) </ i >
90
90
< p >
91
- The current implementation is only a partial implementation and does not yet fully
92
- conform to the Principles of Operation, but it is better than what we had (which
93
- was nothing). Efforts are currently under way to finish the current implementation
94
- to make it fully compliant to the published architecture, but the effort has not
95
- been completed yet, so it might not execute properly under certain situations.
96
- Hopefully it should execute well enough under most common situations however.
91
+ Efforts are currently under way to develop a formal runtest PFPO instruction
92
+ verification test for the current implementation to prove that it fully complies
93
+ with the published architecture, but the effort has not been completed yet.
94
+ Nevertheless, the current implementation is < i > believed</ i > to fully comply
95
+ with the Principles of Operation even though we can't yet prove that.
97
96
</ p >
98
97
99
98
100
- < dt > VMFPLC2 VM/CMS tape utility enhanced
99
+ < dt > Enhanced VMFPLC2 VM/CMS tape utility
101
100
< dd >
102
101
< p >
103
102
The VMFPLC2 tape utility has been greatly enhanced and now supports the scan
@@ -108,7 +107,7 @@ <h2>Release notes for SDL Hyperion 4.2 <small> (under development) </smal
108
107
</ p >
109
108
110
109
111
- < dt > System/370/390 Vector Facility has been disabled again
110
+ < dt > System/370/390 Vector Facility has been re- disabled
112
111
< dd >
113
112
< p >
114
113
It was a mistake to enable the System/370 and System/390 Vector Facility
@@ -144,20 +143,22 @@ <h2>Release notes for SDL Hyperion 4.2 <small> (under development) </smal
144
143
</ p >
145
144
146
145
147
- < dt > Breakpoint/Stepping commands optional ASID parameter
146
+ < dt > Optional ASID parameter added to breakpoint/stepping commands
148
147
< dd >
149
148
< p >
150
149
The < code > b</ code > (breakpoint) and < code > s</ code > (stepping) commands
151
150
now support an optional < b > < code > asid</ code > </ b > (< b > A</ b > ddress < b > S</ b > pace
152
151
< b > ID</ b > entifier) parameter. If specified, the breakpoint or stepping
153
- will only occur if the instruction being executed is < i > both</ i > within
152
+ will only occur if the instructions being executed are < i > both</ i > within
154
153
the specified address range < i > < u > and</ u > </ i > are being executed by the
155
- specified address space. The breakpoint or stepping will < i > not</ i >
156
- occur for any other address spaces even if they are within the specified
157
- address range.
154
+ specified address space. If specified, the breakpoint or stepping will
155
+ < i > not</ i > occur for any other address spaces even if the instructions are
156
+ within the specified address range. If the optional ASID is not specified,
157
+ breakpoints or steppings occurs normally as before (i.e. if the instruction
158
+ being executed is within the specified range).
158
159
< p >
159
160
For more information refer to the < code > help</ code > command display
160
- for the < code > b</ code > and/or < code > s</ code > commands.
161
+ for the < code > b</ code > and/or < code > s</ code > commands (i.e. "help b", "help s", etc) .
161
162
</ p >
162
163
163
164
@@ -166,9 +167,24 @@ <h2>Release notes for SDL Hyperion 4.2 <small> (under development) </smal
166
167
< p >
167
168
Release 4.2 introduces a new configuration file option called
168
169
< a href ="hercconf.html#PANOPT "> < code > PANOPT</ code > </ a >
169
- that controls how emulated device files are displayed. The < code > NAMEONLY</ code >
170
- option will display only the emulated device file's base filename, whereas
171
- < u > < code > FULLPATH</ code > </ u > displays the device file's full path like before.
170
+ that controls how emulated device files are displayed on the screen. The
171
+ < code > NAMEONLY</ code > option will display only the emulated device file's
172
+ base filename, whereas < code > FULLPATH</ code > displays the device file's
173
+ full path like before.
174
+ </ p >
175
+
176
+
177
+ < dt > New Diagnose F09 instruction
178
+ < dd >
179
+ < p >
180
+ Release 4.2 introduces a new Diagnose F09 instruction that is essentially
181
+ an enhanced version of the existing Diagnose F08 instruction providing
182
+ access to Hercules's internal instruction counter. For detailed usage
183
+ information please refer to the
184
+ < a href ="https://github.com/SDL-Hercules-390/hyperion/issues/211#issuecomment-497233616 ">
185
+ final comment</ a > in GitHub Issue #211:
186
+ < a href ="https://github.com/SDL-Hercules-390/hyperion/issues/211 ">
187
+ "Diagnose F08 Improvement"</ a > .
172
188
</ p >
173
189
174
190
0 commit comments