Re: xlf compiler bug?
- From: nospam@xxxxxxxxxxxxx (Richard Maine)
- Date: Mon, 21 May 2007 18:21:40 -0700
Googleer <stocksami@xxxxxxxxxxxxx> wrote:
It was a multi-dimensioned array and only one of the dimensions was
zero. I was able to assign values to the array. It appears that xldb
was confused by the zero. I would think it should have showed me the
portion of the array that had non-zero dimensions.
There is no portion that has non-zero dimensions. If any of the
dimensions is zero extent, then the whole array is zero sized, the array
size being the product of the extents. You say that you were able to
assign values to it. What are the elements that you think you managed to
assign values to? In particular, what index value did thay have in the
dimension that was zero extent? Whatever index value they had in that
dimension, it was an invalid one, as the zero extent means there are no
valid ones.
Did you have bounds checking turned on? Sounds to me like you set values
that were out of bounds, but didn't get caught.
Xldb is a really handy tool for debugging, but it isn't perfect.
While I don't know xldb in particular, I suspect that the first part of
that is true, and I'm sure that the second part is. :-)
--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.
- Follow-Ups:
- Re: xlf compiler bug?
- From: Googleer
- Re: xlf compiler bug?
- References:
- xlf compiler bug?
- From: Googleer
- Re: xlf compiler bug?
- From: Googleer
- Re: xlf compiler bug?
- From: Richard Maine
- Re: xlf compiler bug?
- From: Googleer
- xlf compiler bug?
- Prev by Date: Re: c = inverse(sqrt(epsilon nought *mu nought))
- Next by Date: Re: question about logarithm in fortran
- Previous by thread: Re: xlf compiler bug?
- Next by thread: Re: xlf compiler bug?
- Index(es):
Relevant Pages
|