------- Comment #6 from brooks at gcc dot gnu dot org 2007-05-17 22:45 -------
Yeah, this is to be expected, I think. Holleriths store the memory
representation but not the "semantic" representation of their value, and
transfer tries to fold things and gets confused.
There's probably an easy fix for this, or there's also the fact that when the
transfer implementation is updated to do proper in-memory stuff (to account for
things like TRANSFER(TRANSFER(34, .TRUE.), 0) which should return 34), fixing
this will fall out of it if done right.
I'm accepting this because I plan to do the latter in a way that will fix this
as a side effect. However, if someone cares, I can also put in a code to do
this appropriately in the short term as well.
--
brooks at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |brooks at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
Last reconfirmed|2007-05-17 17:33:59 |2007-05-17 22:45:07
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31972
