This is the mail archive of the gcc@gcc.gnu.org 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] |
Other format: | [Raw text] |
Richard Henderson wrote:
On Mon, Dec 16, 2002 at 11:46:57PM +0100, Toon Moene wrote:Yes, that's impossible to express in Fortran (90/95/F2K), hence we don't have to worry about it.
[ The way to do this in Fortran is to write:
IF (ASSOCIATED(P)) THEN
.... USE P
ELSE
.... BETTER KEEP YOUR PAWS OFF ....
ENDIF
Yes, it might well be that I do not understand the purpose of the prohibition of this optimization in GCC. Obviously (he says now :-) I expect optimizations to conserve the "correct program" property, i.e. if A is a program in Fortran then opt(A) also is a program in Fortran (note that this property is - much - weaker than: encodes the same computation).Um, isn't this still exactly what I talked about? The use of P is protected by a conditional.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |