public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "skoerner at nvidia dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107223] New: GCC 12.2 fails compilation on Linux PowerPC In function 'bessel_jn_r17': Date: Tue, 11 Oct 2022 21:24:17 +0000 [thread overview] Message-ID: <bug-107223-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107223 Bug ID: 107223 Summary: GCC 12.2 fails compilation on Linux PowerPC In function 'bessel_jn_r17': Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: skoerner at nvidia dot com Target Milestone: --- ../.././libgfortran/generated/bessel_r17.c: In function 'bessel_jn_r17': ../.././libgfortran/generated/bessel_r17.c:83:20: error: implicit declaration of function 'jnq'; did you mean 'jnl'? [-Werror=implicit-function-declaration] 83 | last1 = MATHFUNC(jn) (n2, x); | ^~ ../.././libgfortran/generated/bessel_r17.c:34:28: note: in definition of macro 'MATHFUNC' 34 | #define MATHFUNC(funcname) funcname ## q | ^~~~~~~~ ../.././libgfortran/generated/bessel_r17.c: In function 'bessel_yn_r17': ../.././libgfortran/generated/bessel_r17.c:153:20: error: implicit declaration of function 'ynq'; did you mean 'ynl'? [-Werror=implicit-function-declaration] 153 | last1 = MATHFUNC(yn) (n1, x); | ^~ ../.././libgfortran/generated/bessel_r17.c:34:28: note: in definition of macro 'MATHFUNC' 34 | #define MATHFUNC(funcname) funcname ## q | ^~~~~~~~ 4.14.0-115.el7a.ppc64le RHEL 7.6
next reply other threads:[~2022-10-11 21:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-11 21:24 skoerner at nvidia dot com [this message] 2022-10-11 23:30 ` [Bug libfortran/107223] " pinskia at gcc dot gnu.org 2022-10-12 7:10 ` skoerner at nvidia dot com
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-107223-4@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: linkBe 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).