public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/45106] casting of variadic function pointers to normal function pointers causes segfaults on 64bit systems
Date: Wed, 28 Jul 2010 14:01:00 -0000 [thread overview]
Message-ID: <20100728140140.334.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45106-19494@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from rguenth at gcc dot gnu dot org 2010-07-28 14:01 -------
(In reply to comment #4)
> Subject: Re: casting of variadic function pointers to normal
> function pointers causes segfaults on 64bit systems
>
> I was afraid of this answer.
> However in my application, I have no clue which type of function pointer
> is transferred. Thus, I should always cast to the variadic function
> pointer in order to define the %al register?
>
> Cheers, Robert
That doesn't work either. You have to pass around some cookie that
tells you the function prototype and cast to the appropriate one.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45106
prev parent reply other threads:[~2010-07-28 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 11:47 [Bug c/45106] New: " robert dot haschke at uni-bielefeld dot de
2010-07-28 11:53 ` [Bug c/45106] " robert dot haschke at uni-bielefeld dot de
2010-07-28 11:53 ` robert dot haschke at uni-bielefeld dot de
2010-07-28 11:57 ` jakub at gcc dot gnu dot org
2010-07-28 12:04 ` rhaschke at techfak dot uni-bielefeld dot de
2010-07-28 12:26 ` schwab at linux-m68k dot org
2010-07-28 14:01 ` rguenth at gcc dot gnu dot org [this message]
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=20100728140140.334.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: 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).