From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15260 invoked by alias); 13 May 2010 14:46:32 -0000 Received: (qmail 15079 invoked by uid 48); 13 May 2010 14:46:18 -0000 Date: Thu, 13 May 2010 14:46:00 -0000 Message-ID: <20100513144618.15078.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/44116] 64bit inodes for source code causes "Value too large for defined data type" (XFS,inode64) In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "amonakov 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: 2010-05/txt/msg01398.txt.bz2 ------- Comment #1 from amonakov at gcc dot gnu dot org 2010-05-13 14:46 ------- > root@matylda1: /mnt/data/kasparek# LC_ALL=C gcc -o test.o test-10356.c > cc1: error: test-10356.c: Value too large for defined data type > The first this I need to help with is how to > check if the code that causes this (expect somewhere is used 32bit variable to > store the inode) is from gcc itself or it is some third-party library. I Execute gcc -o test.o test-10356.c -### 2>&1 | grep cc1 to get the cc1 command line. Then use gdb --args to debug the compiler. Getting a backtrace before the abort would be nice. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44116