While I have seen similar behavior on other compilers, I interpret the downgrading of extended precision to double as an indication that extended precision is not supported (for one reason or another).
To be a little more specific, I want to know if tcc does support extended precision like gcc does (~18 significant digits) without just downgrading to the double precision (15 significant digits). And if so, why that doesn't work for me. 2014-09-06 17:26 GMT+02:00 Stephan Beal <[email protected]>: > On Sat, Sep 6, 2014 at 4:38 PM, Mads <[email protected]> wrote: > >> I wish to use extended precision in functions compiled by tcc during >> execution. >> Unfortunately, it appears that for any functions compiled by tcc, sizeof >> (double) == sizeof (long double) - and I haven't got the slightest clue >> whether it's intended, if it's a bug or if I'm missing some flags. >> > > According to C, it's not a bug: a long double must have "at least as much > precision" as a double, and a double must have "at least as much precision" > as a float. > > http://en.wikipedia.org/wiki/Long_double#long_double_in_C > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of > those who insist on a perfect world, freedom will have to do." -- Bigby Wolf > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
