From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-161553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 11316 invoked by alias); 11 Oct 2005 05:50:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 11299 invoked by uid 48); 11 Oct 2005 05:49:58 -0000
Date: Tue, 11 Oct 2005 05:50:00 -0000
Subject: [Bug libfortran/24305]  New: Complex(10) formatted IO is broken.
X-Bugzilla-Reason: CC
Message-ID: <bug-24305-8500@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "jblomqvi at cc dot hut dot fi" <gcc-bugzilla@gcc.gnu.org>
X-SW-Source: 2005-10/txt/msg01251.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

The problem is that the IO routines assume kind==size, and complex numbers are
handled as two reals, advancing a pointer between doing the IO. For types with
padding such as complex(10) this breaks as the pointer is advanced 10 bytes
instead of 12 (or 16 on IA64, x86-64).

It should be noted that the patch proposed for 24174 also fixes complex(10)
formatted output.


-- 
           Summary: Complex(10) formatted IO is broken.
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jblomqvi at cc dot hut dot fi
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24305