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 libfortran/107223] GCC 12.2 fails compilation on Linux PowerPC In function 'bessel_jn_r17':
Date: Wed, 12 Oct 2022 07:10:30 +0000	[thread overview]
Message-ID: <bug-107223-4-5Pq7x3sOVf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107223-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107223

--- Comment #2 from Sebastian Koerner <skoerner at nvidia dot com> ---
I used these packages (from source)
mpfr-4.1.0
gmp-6.2.1
mpc-1.2.1
binutils-2.38
gcc-12.2.0
isl-0.24

and this configure line
./configure --prefix=<foo>  --enable-gold --enable-plugin
--enable-languages=c,c++,fortran,objc,obj-c++ --with-gcc-major-version-only
--enable-shared --enable-static --disable-multilib --without-included-gettext
--enable-threads=posix --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --enable-linker-build-id --disable-libquadmath
--disable-libquadmath-support --enable-default-pie --enable-secureplt
--enable-multiarch --disable-werror  --with-cpu=power8
--enable-targets=powerpcle-linux --with-long-double-128
--enable-checking=release --build=powerpc64le-unknown-linux-gnu
--host=powerpc64le-unknown-linux-gnu --target=powerpc64le-unknown-linux-gnu

Now that I read it: disable-quadmath? But why is working on gcc 11.3.0 and with
12.2.0 on x86 and aarch64?

      parent reply	other threads:[~2022-10-12  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 21:24 [Bug fortran/107223] New: " skoerner at nvidia dot com
2022-10-11 23:30 ` [Bug libfortran/107223] " pinskia at gcc dot gnu.org
2022-10-12  7:10 ` skoerner at nvidia dot com [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=bug-107223-4-5Pq7x3sOVf@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).