From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3388 invoked by alias); 13 Jul 2009 18:30:19 -0000 Received: (qmail 3222 invoked by uid 48); 13 Jul 2009 18:30:04 -0000 Date: Mon, 13 Jul 2009 18:30:00 -0000 Message-ID: <20090713183004.3221.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/40734] ICE on attempt to compile trivial Fortran program In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "al dot danial at ngc 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: 2009-07/txt/msg01046.txt.bz2 ------- Comment #3 from al dot danial at ngc dot com 2009-07-13 18:30 ------- (In reply to comment #1) > Fortran reports are never anything but "normal". > > However, would you really expect that a compiler would be released that can't > handle code like the one quoted? I find it hard to believe, especially on a > platform as common as i686-pc-linux-gnu. > > Does the C-compiler work? Something like ... > > $> cat hello.c > #include > int main() { > printf("hello\n"); > return 0; > } > > $> gcc hello.c && ./a.out > > If not, I'd check configuration, compilation and installation. The C compiler works fine. Yes, I'm puzzled by the inability of gfortran to work at all. For what it's worth, I also built an x86_64 installation of 4.4.0 and on it gfortran works perfectly. My build procedure on the i686 machine is identical to the procedure for x86_64 (except for the obvious difference of pointing to 32 bit libraries instead of 64 bit for GMP and MPFR). I agree the problem is most likely on my end however I'm at a loss to figure out why. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40734