public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "al dot danial at ngc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40734] ICE on attempt to compile trivial Fortran program
Date: Mon, 13 Jul 2009 18:30:00 -0000 [thread overview]
Message-ID: <20090713183004.3221.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40734-17942@http.gcc.gnu.org/bugzilla/>
------- 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 <stdio.h>
> 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
next prev parent reply other threads:[~2009-07-13 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 17:19 [Bug fortran/40734] New: " al dot danial at ngc dot com
2009-07-13 18:00 ` [Bug fortran/40734] " dfranke at gcc dot gnu dot org
2009-07-13 18:13 ` jvdelisle at gcc dot gnu dot org
2009-07-13 18:30 ` al dot danial at ngc dot com [this message]
2009-07-13 18:33 ` al dot danial at ngc dot com
2009-07-13 18:42 ` jakub at gcc dot gnu dot org
2009-07-13 18:51 ` al dot danial at ngc dot com
2009-07-13 21:13 ` al dot danial at ngc dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090713183004.3221.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).