On Thu, Nov 19, 2020 at 08:03:02AM -0600, Segher Boessenkool wrote: > On Thu, Nov 19, 2020 at 03:08:05AM -0500, Michael Meissner wrote: > > On Wed, Nov 18, 2020 at 04:29:09PM -0600, Segher Boessenkool wrote: > > > Mike, please add a comment, what number it represents? Okay for trunk > > > with that, thanks. > > > > > > (Should those not be define in some header though?) > > > > When long double is IBM extended double, then LDBL_MAX, etc. is set with > > math.h > > (and the __ version created by the compiler). We don't have min/max for the > > funky MD only floating point numbers defined. I got the number by printing > > LDBL_MAX in fact and just pasting that in. > > Sure -- I am suggesting to always define __IBM128_MAX__ and the like, > which then can be used to define LDBL_MAX, but also can be used > directly.
I have posted patches for this as a new set of patches. Rather than trying to create IBM 128-bit long double min/max/etc. defines, I just marked the test as needing IBM 128-bit long double. I did look into providing defines for these. Unfortunately the function that creates these (builtin_define_float_constants) is static. And the caller of that function (c_cpp_builtins) does not have a target hook or other method to provide for these defines for MD specific floating point types. -- Michael Meissner, IBM IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA email: meiss...@linux.ibm.com, phone: +1 (978) 899-4797
