public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49962] [OOP] ICE when using type-bound function returning vector Date: Thu, 04 Aug 2011 17:59:00 -0000 [thread overview] Message-ID: <bug-49962-4-iQLJOTmJuz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49962-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49962 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |janus at gcc dot gnu.org Summary|"internal compiler error" |[OOP] ICE when using |when using type-bounded |type-bound function |function returning vector |returning vector --- Comment #4 from janus at gcc dot gnu.org 2011-08-04 17:58:55 UTC --- This is certainly a duplicate of PR49961, and has been fixed by r160622, which could also be backported to the 4.5 branch. Since we got two apparently independent bug reports for this on the same day: Is there any "real-world" code which is affected by this bug? Or in other words: How did you come across this bug?
next prev parent reply other threads:[~2011-08-04 17:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-03 14:17 [Bug fortran/49962] New: "internal compiler error" when using type-bounded " wangmianzhi1 at linuxmail dot org 2011-08-03 14:23 ` [Bug fortran/49962] " dominiq at lps dot ens.fr 2011-08-03 14:24 ` wangmianzhi1 at linuxmail dot org 2011-08-03 15:22 ` burnus at gcc dot gnu.org 2011-08-04 17:59 ` janus at gcc dot gnu.org [this message] 2011-08-04 18:07 ` [Bug fortran/49962] [OOP] ICE when using type-bound " wangmianzhi1 at linuxmail dot org 2011-08-04 20:30 ` janus at gcc dot gnu.org 2011-08-15 16:06 ` burnus at gcc dot gnu.org 2011-08-16 17:26 ` janus at gcc dot gnu.org 2011-08-16 21:24 ` janus at gcc dot gnu.org 2011-08-16 21:26 ` janus 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-49962-4-iQLJOTmJuz@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).