public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100914] Bind(c): errors handling complex
Date: Sat, 05 Jun 2021 12:20:18 +0000 [thread overview]
Message-ID: <bug-100914-4-zajZYokkUd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100914-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100914
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-06-05
Status|UNCONFIRMED |WAITING
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
On my system I get
% gfc pr100914.f90 pr100914.c
pr100914.c: In function 'c_vrfy_float_complex':
pr100914.c:61:22: warning: implicit declaration of function 'CMPLXF'
[-Wimplicit-function-declaration]
61 | if ((cabsf (*ip-(CMPLXF((float)(i+1),
(float)(2*(i+1)))))>(float)0.0))
| ^~~~~~
pr100914.c: In function 'c_vrfy_double_complex':
pr100914.c:98:21: warning: implicit declaration of function 'CMPLX'
[-Wimplicit-function-declaration]
98 | if ((cabs (*ip-(CMPLX((double)(i+1),
(double)(2*(i+1)))))>(double)0.0))
| ^~~~~
Undefined symbols for architecture x86_64:
"_CMPLX", referenced from:
_c_vrfy_double_complex in ccFYXXYa.o
_c_vrfy_float128_complex in ccFYXXYa.o
"_CMPLXF", referenced from:
_c_vrfy_float_complex in ccFYXXYa.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
next prev parent reply other threads:[~2021-06-05 12:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 19:17 [Bug fortran/100914] New: " jrfsousa at gcc dot gnu.org
2021-06-04 19:18 ` [Bug fortran/100914] " jrfsousa at gcc dot gnu.org
2021-06-05 12:20 ` dominiq at lps dot ens.fr [this message]
2021-06-06 1:08 ` jrfsousa at gcc dot gnu.org
2021-06-06 1:09 ` jrfsousa at gcc dot gnu.org
2021-06-13 18:46 ` jrfsousa at gcc dot gnu.org
2021-06-13 18:47 ` jrfsousa at gcc dot gnu.org
2021-06-18 11:02 ` dominiq at lps dot ens.fr
2021-09-02 23:42 ` cvs-commit at gcc dot gnu.org
2021-09-03 0:00 ` sandra at gcc dot gnu.org
2021-10-22 2:39 ` sandra at gcc dot gnu.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=bug-100914-4-zajZYokkUd@http.gcc.gnu.org/bugzilla/ \
--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).