From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14297 invoked by alias); 16 Oct 2009 01:41:53 -0000 Received: (qmail 14265 invoked by uid 48); 16 Oct 2009 01:41:39 -0000 Date: Fri, 16 Oct 2009 01:41:00 -0000 Message-ID: <20091016014139.14264.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libfortran/41711] Z format does not support writing KIND=10 reals In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jvdelisle at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-10/txt/msg01419.txt.bz2 ------- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-10-16 01:41 ------- I had a chance to review our code here. It uses gfc_xtoa which resides in runtime\error.c. All of our conversion routines are dependent on GFC_UINTEGER_LARGEST which is platform dependent. I think there is a significant rework we would have to do to support conversion of real(10) to a hex string on all platforms. One possible way would be to embed some special case helper functions in the existing routines. We would be in effect implementing an internal kind=16 integer of sorts for the older x86 machines. i am not sure its worth the effort. For now, I think we need to trap the kind and give a decent error message, possibly at compile time. Any other thoughts. If the demand is there, we could implement this. I just don't think the demand is there. Comments? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41711