Re: [patch] PR93727 Fortran 2018: EX edit descriptor
Jerry D <[email protected]>
| Newsgroups | gmane.comp.gcc.patches,gmane.comp.gcc.fortran |
|---|---|
| Message-ID | <[email protected]> |
On 2/2/26 12:28 PM, Harald Anlauf wrote: > Hi Jerry! > --- snip --- > > I meant: do all platforms which *we* support implement real(10)? > You could > > % grep -r __GFC_REAL_10__ gcc/testsuite/gfortran.dg/ I will investigate this further. > > for similar solutions. > --- snip --- > > Let's see: > > 13.7.2.3.6 EX editing > > The EXw.d and EXw.dEe edit descriptors indicate that the external field > occupies w positions, except when w is zero in which case the processor > selects the field width. The fractional part of the field contains d > hexadecimal digits, except when d is zero in which case the processor > selects the number of hexadecimal digits to be the minimum required so > that the output field is equal to the internal value; ... > > But -0XF.FFFFFP+124 is shorter than -0X1.FFFFFEP+127, so I think > you should recheck. Sorry for the extra work ;-) > >> I am very aware of this. My interpretation is "in which case the processor selects" the number of hexadecimal digits to be what ever minimum it chooses to produce. Keep in mind this is using the built-in C functions to generate the hex string so we do not have a bit string to deal with. The value is correct and it is the minimum the processor produces. Anyone else one to way in on this? I sure don't want to create custom code bit shift this. > > Thanks for that. > > We're getting closer... Eagerly waiting for version 3 ;-) > > Best, > Harald > >>> >>>> >>>> Best, >>>> Harald >>>> --- snip --- >>> >>> Thanks for the review. I will fix these and resubmit. >>> >>> Jerry >>> >>> >