public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30877] Extending intrinsic operators Date: Wed, 21 Mar 2007 14:50:00 -0000 [thread overview] Message-ID: <20070321145020.19866.qmail@sourceware.org> (raw) In-Reply-To: <bug-30877-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-03-21 14:50 ------- Created an attachment (id=13243) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13243&action=view) Patch to fix the problem reported This one is mine. Attached patch (regtested on i686-linux) fixes the failure and, as far as I see, should bring the extension of intrinsic operators completely in line with the standards. I still need to come up with a complete testcase to ensure that I haven't forgotten something along the way. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30877
next prev parent reply other threads:[~2007-03-21 14:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-20 7:52 [Bug fortran/30877] New: incorrect error message for valid code jv244 at cam dot ac dot uk 2007-02-20 16:32 ` [Bug fortran/30877] overloading "operator(*)" for intrinsic type (complex) fails burnus at gcc dot gnu dot org 2007-02-21 21:15 ` pault at gcc dot gnu dot org 2007-02-22 1:35 ` ben_ship at lycos dot com 2007-02-22 3:16 ` ben_ship at lycos dot com 2007-03-21 0:10 ` fxcoudert at gcc dot gnu dot org 2007-03-21 14:02 ` [Bug fortran/30877] Extending intrinsic operators fxcoudert at gcc dot gnu dot org 2007-03-21 14:50 ` fxcoudert at gcc dot gnu dot org [this message] 2007-03-25 9:01 ` fxcoudert at gcc dot gnu dot org 2007-03-25 9:02 ` fxcoudert 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=20070321145020.19866.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).