public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46244] gfc_compare_derived_types is buggy Date: Sun, 02 Oct 2011 17:47:00 -0000 [thread overview] Message-ID: <bug-46244-4-s6BJW67PqJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46244-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46244 --- Comment #17 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-10-02 17:46:44 UTC --- Created attachment 25397 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25397 updated patch for revision 179415 The patch in comment #12 no longer applies cleanly (the changes in resolve.c are now obsolete, I have mechanically replaced four times !gfc_compare_types with !gfc_TK_compatible, although it does not introduce regression, this should be checked by someone understanding the code better than I do). I had also to do a similar change in gcc/fortran/check.c to allow move_alloc_5.f90 and select_type_23.f03 to pass (otherwise they fail with Error: 'from' argument of 'move_alloc' intrinsic at (1) must be the same type and kind as 'to' I have also updated null_1.f90. With these changes I had no regression and my tests passed without the glitch reported in comment #13 (the previous patch probably exposed some rampant bug that has been fixed).
next prev parent reply other threads:[~2011-10-02 17:47 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-30 14:24 [Bug fortran/46244] New: " janus at gcc dot gnu.org 2010-10-30 14:30 ` [Bug fortran/46244] " janus at gcc dot gnu.org 2010-10-30 14:54 ` janus at gcc dot gnu.org 2010-10-30 15:04 ` janus at gcc dot gnu.org 2010-10-30 15:11 ` janus at gcc dot gnu.org 2010-10-30 16:02 ` mikael at gcc dot gnu.org 2010-10-30 16:04 ` mikael at gcc dot gnu.org 2010-11-05 13:56 ` dominiq at lps dot ens.fr 2010-11-05 15:01 ` burnus at gcc dot gnu.org 2010-11-06 13:00 ` burnus at gcc dot gnu.org 2010-11-10 17:45 ` burnus at gcc dot gnu.org 2010-11-10 17:49 ` burnus at gcc dot gnu.org 2011-02-20 16:58 ` mikael at gcc dot gnu.org 2011-02-20 17:01 ` mikael at gcc dot gnu.org 2011-02-20 21:07 ` dominiq at lps dot ens.fr 2011-02-20 22:20 ` dominiq at lps dot ens.fr 2011-02-20 23:18 ` mikael at gcc dot gnu.org 2011-02-21 9:37 ` paul.richard.thomas at gmail dot com 2011-10-02 17:47 ` dominiq at lps dot ens.fr [this message] 2011-10-02 22:06 ` mikael at gcc dot gnu.org 2024-01-19 18:00 ` mikael 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=bug-46244-4-s6BJW67PqJ@http.gcc.gnu.org/bugzilla/ \ --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).