diff options
author | Jakub Jelinek <jakub@redhat.com> | 2024-03-04 11:40:27 +0100 |
---|---|---|
committer | Jakub Jelinek <jakub@redhat.com> | 2024-03-04 11:48:40 +0100 |
commit | dea9ac2a00d1e4126d61b65a8302c2bd523f0b99 (patch) | |
tree | 30dcc7d5fc93ecc3d6fba950bb1ca54ea43cba0a /libgomp/target.c | |
parent | cde50296a19b109909089b91d532d2c8455f5f10 (diff) | |
download | gcc-dea9ac2a00d1e4126d61b65a8302c2bd523f0b99.zip gcc-dea9ac2a00d1e4126d61b65a8302c2bd523f0b99.tar.gz gcc-dea9ac2a00d1e4126d61b65a8302c2bd523f0b99.tar.bz2 |
libgomp: Use void (*) (void *) rather than void (*)() for host_fn type [PR114216]
For the type of the target callbacks we use elsehwere void (*) (void *) and
IMHO should use that for the reverse offload fallback as well (where the actual
callback is emitted using the same code as for host fallback or device kernel
entry routines), even when it is also ok to use void (*) () before C23 and
we aren't building libgomp with C23 yet. On some arches perhaps void (*) ()
could result in worse code generation because calls in that case like casts
to unprototyped functions need to sometimes pass argument in two different spots
etc. so that it deals with both passing it through ... and as a named argument.
2024-03-04 Jakub Jelinek <jakub@redhat.com>
PR libgomp/114216
* target.c (gomp_target_rev): Change host_fn type and corresponding
cast from void (*)() to void (*) (void *).
Diffstat (limited to 'libgomp/target.c')
-rw-r--r-- | libgomp/target.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libgomp/target.c b/libgomp/target.c index 1367e9c..bcc8605 100644 --- a/libgomp/target.c +++ b/libgomp/target.c @@ -3447,7 +3447,7 @@ gomp_target_rev (uint64_t fn_ptr, uint64_t mapnum, uint64_t devaddrs_ptr, if (n == NULL) gomp_fatal ("Cannot find reverse-offload function"); - void (*host_fn)() = (void (*)()) n->k->host_start; + void (*host_fn) (void *) = (void (*) (void *)) n->k->host_start; if ((devicep->capabilities & GOMP_OFFLOAD_CAP_SHARED_MEM) || mapnum == 0) { |