From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 748 invoked by alias); 21 Dec 2007 03:59:33 -0000 Received: (qmail 681 invoked by uid 48); 21 Dec 2007 03:59:19 -0000 Date: Fri, 21 Dec 2007 03:59:00 -0000 Message-ID: <20071221035919.680.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/20366] AIX g++ -D_LARGE_FILES fails to compile #include In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "bugzilla-gcc at thewrittenword dot com" 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: 2007-12/txt/msg01970.txt.bz2 ------- Comment #9 from bugzilla-gcc at thewrittenword dot com 2007-12-21 03:59 ------- (In reply to comment #8) > The issue is whether to default G++ to _LARGE_FILES, as is done for Fortran, > and perform all libstdc++ I/O as 64-bit operations, which will affect > performance. Not everyone may want or need large I/O. There is no way to give > users control over this without imposing it so G++, G++ headers, and libstdc++ > all are self-consistent. The other alternative is another multilib, but there > alredy are too many variants. Why is this? -D_LARGE_FILES simply enables LFS. xlC works with and without -D_LARGE_FILES. Shouldn't G++ work as effectively as xlC? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366