public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/41777] wrong-code shown with EXCITING Date: Wed, 21 Oct 2009 09:11:00 -0000 [thread overview] Message-ID: <20091021091053.13733.qmail@sourceware.org> (raw) In-Reply-To: <bug-41777-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2009-10-21 09:10 ------- Created an attachment (id=18851) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18851&action=view) Slightly reduced test case - needs now only FoX Reduced test case -- still pretty large, but now only depends on FoX. Use similarly to PR 41772: wget http://www.uszla.me.uk/FoX/source/FoX-4.0.4.tar.gz tar xfz FoX-4.0.4.tar.gz cd FoX-4.0.4 && ./configure FC=gfortran && make -j4 gfortran -Iobjs/finclude fox.f90 objs/lib/libFoX_{dom,utils,sax,common,fsys}.a ./a.out In order to see better what goes wrong, patch dom/m_dom_dom.F90's removeChild by adding the PRINT statements: do i = 1, size(arg%childNodes%nodes) print *, 'removeChild: Walking list, i = ', i if (associated(arg%childNodes%nodes(i)%this, oldChild)) then print *, 'removeChild: Walking list, fount it, i_t = ', i_t The gfortran output is then: removeChild: Walking list, i = 1 [...] removeChild: Walking list, i = 9 NOT_FOUND_ERR While g95/NAG f95 have: removeChild: Walking list, i = 1 [...] removeChild: Walking list, fount it, i_t = 4 [...] removeChild: Walking list, i = 9 FoX_NODE_IS_NULL (Afterwards, all core dump. The result that it = 4 is found, can also be seen with the full program, where no segfault occurs.) The needed input.xml can be found in attachment 18846 of PR 41772 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41777
next prev parent reply other threads:[~2009-10-21 9:11 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-21 8:41 [Bug fortran/41777] New: " burnus at gcc dot gnu dot org 2009-10-21 9:11 ` burnus at gcc dot gnu dot org [this message] 2009-10-21 9:12 ` [Bug fortran/41777] " burnus at gcc dot gnu dot org 2009-10-21 9:22 ` [Bug fortran/41777] wrong-code with FoX, related to ASSOCIATE( Ptr1, Ptr2) burnus at gcc dot gnu dot org 2009-10-21 12:09 ` [Bug fortran/41777] Wrong-code with POINTER-returning GENERIC function burnus at gcc dot gnu dot org 2009-10-25 14:33 ` burnus at gcc dot gnu dot org 2009-10-25 14:44 ` burnus at gcc dot gnu dot org 2009-10-25 18:34 ` dominiq at lps dot ens dot fr 2009-10-28 10:18 ` burnus at gcc dot gnu dot org 2009-10-28 10:38 ` burnus at gcc dot gnu dot org 2009-10-28 15:03 ` burnus at gcc dot gnu dot org 2009-10-28 15:47 ` burnus at gcc dot gnu dot org 2009-10-28 16:27 ` dominiq at lps dot ens dot fr 2009-10-29 15:25 ` burnus at gcc dot gnu dot org 2009-10-29 15:28 ` burnus at gcc dot gnu dot org 2009-10-29 16:44 ` burnus at gcc dot gnu dot org 2009-10-30 15:18 ` burnus at gcc dot gnu dot org 2009-11-27 14:28 ` mrestelli at gmail dot com 2010-02-02 10:00 ` burnus at gcc dot gnu dot org 2010-02-02 10:00 ` burnus at gcc dot gnu dot 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=20091021091053.13733.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).