public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: colin@field.medicine.adelaide.edu.au
To: gcc-gnats@gcc.gnu.org
Subject: c++/6432: __builtin_apply() rejected by g++ - per PR 102
Date: Tue, 23 Apr 2002 16:46:00 -0000 [thread overview]
Message-ID: <20020423234304.8F39C2F039@colin.sharedtech.dyndns.org> (raw)
>Number: 6432
>Category: c++
>Synopsis: __builtin_apply() rejected by g++ - per PR 102
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Tue Apr 23 16:46:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Colin McCormack
>Release: gcc version 2.95.4 20011002 (Debian prerelease)
>Organization:
>Environment:
System: Linux colin.sharedtech.dyndns.org 2.4.18-686 #2 Wed Mar 20 20:21:31 EST 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
>Description:
g++ rejects all possible constructions of __builtin_apply() by requiring the second argument to be of an impossible type, with an error: argument passing to `void * ()(unsigned int)' from `void *'. Please note the impossible type `void * () (unsigned int)'
>How-To-Repeat:
run g++ over the following code:
----
extern void fn1();
void fn (int b){
__builtin_apply( (void (*)())fn1,
__builtin_apply_args(),
32);
}
----
NB: this bug was reported in Problem Report 102 on March 12th 2000, and was closed in error. The bug is, and has been, causing my GPL'd project a great deal of difficulty, and its fix should be straight forward.
>Fix:
There is no fix or workaround possible within g++
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-23 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 16:46 colin [this message]
2002-04-23 16:58 jason
2002-04-23 17:16 Andrew Pinski
2002-04-23 17:16 Colin McCormack
2002-04-23 18:46 Jason Merrill
2002-04-26 2:10 nathan
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=20020423234304.8F39C2F039@colin.sharedtech.dyndns.org \
--to=colin@field.medicine.adelaide.edu.au \
--cc=gcc-gnats@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).