public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19520] New: protected function pointer doesn't work right
Date: Wed, 19 Jan 2005 00:25:00 -0000	[thread overview]
Message-ID: <20050119002432.19520.hjl@lucon.org> (raw)

Protected function pointer doesn't work right. For pointer to protected
function, gcc should treat it as if it is normal.

-- 
           Summary: protected function pointer doesn't work right
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl at lucon dot org
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: x86_64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19520


             reply	other threads:[~2005-01-19  0:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  0:25 hjl at lucon dot org [this message]
2005-01-19  0:27 ` [Bug target/19520] " hjl at lucon dot org
2005-01-19  0:34 ` pinskia at gcc dot gnu dot org
2005-01-19  0:36 ` hjl at lucon dot org
2005-01-19  0:41 ` hjl at lucon dot org
2005-01-19  0:47 ` pinskia at gcc dot gnu dot org
2005-01-19  0:56 ` pinskia at gcc dot gnu dot org
2005-01-19  1:48 ` hjl at lucon dot org
2005-01-19  3:11 ` pinskia at gcc dot gnu dot org
2005-01-19  3:31 ` pinskia at gcc dot gnu dot org
2005-01-19  3:41 ` pinskia at gcc dot gnu dot org
2005-01-20 19:28 ` hjl at lucon dot org
2005-01-20 22:34 ` hjl at lucon dot org
2005-01-21  6:35 ` ian at airs dot com
2005-01-21  6:36 ` ian at airs dot com
2005-01-21  6:47 ` hjl at lucon dot org
2005-01-24 18:35 ` hjl at lucon dot org
2005-02-02 13:16 ` amodra at bigpond dot net dot au
2005-02-02 16:17 ` hjl at lucon 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=20050119002432.19520.hjl@lucon.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: link
Be 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).