public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36192] ICE with wrong index types and bad parens Date: Sun, 11 May 2008 16:40:00 -0000 [thread overview] Message-ID: <20080511164002.16690.qmail@sourceware.org> (raw) In-Reply-To: <bug-36192-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from dominiq at lps dot ens dot fr 2008-05-11 16:40 ------- For the record: after fixing the syntax errors, the executable gives an infinite loop when compiled with gfortran 4.3.0 on *i-apple-darwin9 and 4.4.0 (patched) on i686-apple-darwin9, but not on 4.4.0 (also patched) on powerpc-apple-darwin9. The infinite loop comes from a nasty (even for trained eyes) typo which leaves the intent(out) dummies xn and vn unset on return of subroutine step (since the code seems to be some homework, I leave the reporter complete the debugging himself). The points of interest for the gfortran maintainers are: (1) are there other platforms on which there is no infinite loop? and if yes why? (2) I think the problem could be diagnosed at compiled time (possibly with -O only). If it can now, I did not find the right option. If not, should I open a pr along this line or would it deemed too difficult to implement? Final note, the code has at least another bug (hint: set n=2, d=3 and compile with -fbounds-check). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36192
next prev parent reply other threads:[~2008-05-11 16:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-09 17:47 [Bug fortran/36192] New: ICE: Segmentation fault doko at ubuntu dot com 2008-05-09 17:47 ` [Bug fortran/36192] " doko at ubuntu dot com 2008-05-09 18:05 ` kargl at gcc dot gnu dot org 2008-05-09 18:16 ` kargl at gcc dot gnu dot org 2008-05-09 20:07 ` [Bug fortran/36192] ICE with wrong index types and bad parens jvdelisle at gcc dot gnu dot org 2008-05-11 16:40 ` dominiq at lps dot ens dot fr [this message] 2008-10-01 12:11 ` dominiq at lps dot ens dot fr 2009-12-29 16:38 ` debian-gcc at lists dot debian dot org 2009-12-29 18:38 ` kargl at gcc dot gnu dot org 2009-12-29 18:58 ` kargl at gcc dot gnu dot org 2009-12-30 0:34 ` kargl at gcc dot gnu dot org 2009-12-30 0:44 ` kargl at gcc dot gnu dot org [not found] <bug-36192-4@http.gcc.gnu.org/bugzilla/> 2015-10-25 18:06 ` kargl at gcc dot gnu.org 2015-10-26 17:39 ` kargl at gcc dot gnu.org 2015-10-30 16:46 ` kargl at gcc dot gnu.org 2015-10-30 17:02 ` kargl at gcc dot gnu.org
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=20080511164002.16690.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: linkBe 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).