public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boaz at hishome dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11893] New: stdcall pointers to member-functions handled wrong
Date: Tue, 12 Aug 2003 11:14:00 -0000	[thread overview]
Message-ID: <20030812111410.11893.boaz@hishome.net> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: stdcall pointers to member-functions handled wrong
           Product: gcc
           Version: 3.2.2
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: boaz at hishome dot net
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: i386-pc-linux

the compiler will not let me declare an __stdcall__ pointer to function member
and code will than SEGFAULT on invocation of the member pointer.  This is not
the case for Regular pointers to functions. ( The compiler will also issue a
warning  on mismatch.)

Listing of the Error: (BAD)

class AFoo
{
public:
    __attribute__((__stdcall__))
    void foo(int i ,int ii ,int iii) ;
} ;

__attribute__((__stdcall__))
void AFoo::foo(int i ,int ii ,int iii)
{
    return ;
}

int main()
{
  AFoo afoo ;
  void ( AFoo::*func)(int,int,int) ;
  func = &AFoo::foo ;

  for(int i=0 ; i < 0x8000000 ;i++)
     (afoo.*func)(1,2,3) ; // SEGFAULT or SEGIL when stack is Exhausted
  return 0 ;
}

any attempt  to place the __atribute__((stdcall)) in the pointer declaration
causes a compilation error. With out it the code will SEGFAULT.

If declaring a regular pointer to function than no compilation error is issued 
and all is well.

Listing of Regular function pointer: (GOOD)

void __attribute__((stdcall)) foo(int i ,int ii ,int iii)
{
}

int main()
{
  void ( __attribute__((stdcall)) *func)(int,int,int) = &foo ;

  for(int i=0 ; i < 0x8000000 ;i++)
     (func)(1,2,3) ;

  return 0 ;
}

removing the __attribute__((stdcall)) from the *func declaration will rightfully
issue a warning ( should be an error if you ask me, type mismatch).
But Not so on our first example.


             reply	other threads:[~2003-08-12 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 11:14 boaz at hishome dot net [this message]
2003-08-12 12:53 ` [Bug c++/11893] " pinskia at gcc dot gnu dot org
2003-08-12 13:17 ` boaz at hishome dot net
2003-08-12 13:26 ` pinskia at gcc dot gnu dot org
2003-08-12 13:34 ` pinskia at gcc dot gnu dot org
2003-08-12 13:49 ` boaz at hishome dot net
2003-08-12 13:53 ` pinskia at gcc dot gnu dot org
2003-08-13 11:49 ` boaz at hishome dot net
2003-08-23  1:17 ` dhazeghi at yahoo dot com
2004-01-01  7:08 ` pinskia 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=20030812111410.11893.boaz@hishome.net \
    --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).