This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Change definition of complex::norm

Brad Lucier <> writes:

| > | There is a small group of arguments for which this
| > | formula gives zero when the current formula gives a nonzero result,
| > | but this now seems to me to be irrelevant---there are many nonzero z
| > | for which both formulas give zero for the norm, and the fact that
| > | there are a few more of these cases with the simpler formula does not
| > | seem important to me.
| > 
| > I presume we disagree on exactly where the line should be drwan. From
| > my point of view, I consider norm() should deliver an answer as close
| > as possible to the real value; that means, for non-subnormal a value
| > acceptable with respect to relative error criterion, and for
| > subnormal, a value acceptable with respect to absolute error criterion.
| > Which is why I prefer to retain the current implementation for norm().
| Perhaps I wasn't clear in my previous post.
| My point (which was in the part of my post that you don't quote)

Sorry, there wasn't a deliberate decision on my part to transmute your
posting.  I just wanted to quote the part of your post I do not agree

|  is
| that the formula
| norm(z) = real(z)^2 + imag(z)^2
| does give good relative error for normal results, and good absolute
| error for denormal results.

This isn't the case in the test you posted.  Did I misread it?

| I should point out that all this is simpler on x86 *if* one can
| assume that all floating-point register spills are spilt to extended
| precision (which we can't assume with the current gcc).  Then the two formulas
| abs(z) = sqrt(real(z)^2 + imag(z)^2)
| and
| norm(z) = real(z)^2 + imag(z)^2
| provide full accuracy and safety for both double- and single-precision
| types _Tp, and one would need the more complicated formulas only for
| extended-precision arguments.

We have to support float, double, long double.  And since we're
intending to support non specified aritmetic types, I think we should
also support the extended precision arguments.

-- Gaby

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]