public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "me at larbob dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64 Date: Sat, 17 Jul 2021 17:14:14 +0000 [thread overview] Message-ID: <bug-61577-4-Qv7k56CflK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577 --- Comment #249 from Larkin Nickle <me at larbob dot org> --- I am still unable to replicate a proper 11.1 build against 2.36 gas. Here's my process: HP GCC 4.7.1 -> GCC 4.7.4: ../../sources/gcc-4.7.4/configure --prefix=/usr/util/toolchain/gcc-4.7.4 --w ith-as=/opt/hp-gcc/bin/as --enable-languages=c,c++ --disable-nls -> 4.9.2: ../../sources/gcc-4.9.2/configure --disable-libgomp --with-as=/opt/hp-gcc/bi n/as --enable-languages=c,c++ --prefix=/usr/util/toolchain/gcc-4.9.2 --disable-n ls Then, I compiled binutils 2.36 (w/ -mlp64), gmp 6.2.1, mpfr 4.1.0, and mpc 1.2.1 with HP GCC 4.7.1. All GMP tests passed except for `t-printf`, all mpfr tests passed except `tasprintf`, and all mpc tests passed. These results are the same as John's except his `t-printf` passes with GMP. Then, I compile GCC 11.1.0 with GCC 4.9.2: ../../sources/gcc-11.1.0/configure --prefix=/usr/util/toolchain/gcc-11.1.0 - -enable-comdat --disable-libgomp --disable-nls --with-as=/usr/util/toolchain/bin utils-2.36/bin/as --with-gmp=/usr/util/toolchain/gmp-6.2.1 --with-mpfr=/usr/util /toolchain/mpfr-4.1.0 --with-mpc=/usr/util/toolchain/mpc-1.2.1 --enable-language s=c,c++ --with-dwarf2 First it errors out when compiling charset.c: ../../../sources/gcc-11.1.0-new/libcpp/charset.c: In function 'cset_converter init_iconv_desc(cpp_reader*, const char*, const char*)': ../../../sources/gcc-11.1.0-new/libcpp/charset.c:695:1: internal compiler error: in plus_constant, at explow.c:101 695 | } | ^ libbacktrace could not find executable to open Then, if libcpp's Makefile is patched so that charset.c is built with -O1, I eventually run into other errors: ../../../../sources/gcc-11.1.0-new/libgcc/libgcov-interface.c: In function 'gcov_clear': ../../../../sources/gcc-11.1.0-new/libgcc/libgcov-interface.c:143:1: internal compiler error: Illegal instruction 143 | } | ^ libbacktrace could not find executable to open After making that compile with -O1: ../../../sources/gcc-11.1.0/zlib/inftrees.c: In function 'inflate_table': ../../../sources/gcc-11.1.0/zlib/inftrees.c:32:19: internal compiler error: Illegal instruction 32 | int ZLIB_INTERNAL inflate_table(type, lens, codes, table, bits, work) | ^~~~~~~~~~~~~ libbacktrace could not find executable to open I am only able to get a build of 11.1 with BOOT_CFLAGS="-g -O1" BOOT_CXXFLAGS="-g -O1". It's worth noting that I have rebuilt gmp with the -O1'd 11.1 build and it fixed the `t-printf` test not passing. I then rebuilt mpfr and mpc against it with 4.7.1 (4.9.2 and 11.1 can't seem to properly compile mpfr) and then tried to build 11.1 against the new builds and still ran into the same issues.
next prev parent reply other threads:[~2021-07-17 17:14 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/> 2014-06-21 11:01 ` [Bug c++/61577] [4.9.0] " FBergemann at web dot de 2015-10-15 11:04 ` [Bug target/61577] " josephpattara at gmail dot com 2015-10-19 11:34 ` josephpattara at gmail dot com 2019-07-05 1:51 ` dave.anglin at bell dot net 2020-02-25 14:55 ` [Bug middle-end/61577] [4.9.0 Regression] " peter.bisroev at groundlabs dot com 2020-04-18 1:11 ` dave.anglin at bell dot net 2020-04-23 15:48 ` peter.bisroev at groundlabs dot com 2020-04-23 16:50 ` dave.anglin at bell dot net 2020-05-02 4:14 ` peter.bisroev at groundlabs dot com 2020-05-02 14:30 ` dave.anglin at bell dot net 2020-05-13 18:03 ` jared.martinsen at fiserv dot com 2020-05-13 19:04 ` dave.anglin at bell dot net 2021-04-16 21:30 ` pinskia at gcc dot gnu.org 2021-04-24 22:21 ` peter at int19h dot net 2021-05-17 9:56 ` jvb at cyberscience dot com 2021-05-19 16:23 ` dave.anglin at bell dot net 2021-05-20 9:19 ` jvb at cyberscience dot com 2021-05-20 13:25 ` dave.anglin at bell dot net 2021-05-20 13:37 ` jvb at cyberscience dot com 2021-05-20 14:02 ` dave.anglin at bell dot net 2021-05-20 14:59 ` jvb at cyberscience dot com 2021-05-20 15:03 ` dave.anglin at bell dot net 2021-05-20 15:16 ` dave.anglin at bell dot net 2021-05-20 17:00 ` dave.anglin at bell dot net 2021-05-20 17:22 ` jvb at cyberscience dot com 2021-06-03 17:19 ` dave.anglin at bell dot net 2021-06-09 9:51 ` jvb at cyberscience dot com 2021-06-09 10:12 ` jvb at cyberscience dot com 2021-07-04 21:56 ` me at larbob dot org 2021-07-05 8:56 ` jvb at cyberscience dot com 2021-07-14 2:51 ` bugzilla-gcc at thewrittenword dot com 2021-07-14 8:35 ` jvb at cyberscience dot com 2021-07-14 15:43 ` jvb at cyberscience dot com 2021-07-14 16:10 ` bugzilla-gcc at thewrittenword dot com 2021-07-14 16:13 ` jvb at cyberscience dot com 2021-07-14 16:37 ` bugzilla-gcc at thewrittenword dot com 2021-07-15 12:09 ` bugzilla-gcc at thewrittenword dot com 2021-07-15 14:22 ` jvb at cyberscience dot com 2021-07-15 14:39 ` bugzilla-gcc at thewrittenword dot com 2021-07-15 14:58 ` jvb at cyberscience dot com 2021-07-15 15:01 ` bugzilla-gcc at thewrittenword dot com 2021-07-15 15:24 ` dave.anglin at bell dot net 2021-07-15 18:48 ` bugzilla-gcc at thewrittenword dot com 2021-07-16 11:33 ` jvb at cyberscience dot com 2021-07-16 12:48 ` bugzilla-gcc at thewrittenword dot com 2021-07-16 12:51 ` bugzilla-gcc at thewrittenword dot com 2021-07-16 13:27 ` jvb at cyberscience dot com 2021-07-16 13:29 ` bugzilla-gcc at thewrittenword dot com 2021-07-17 17:14 ` me at larbob dot org [this message] 2021-07-17 17:39 ` me at larbob dot org 2021-07-17 18:38 ` dave.anglin at bell dot net 2021-07-18 2:02 ` bugzilla-gcc at thewrittenword dot com 2021-07-18 12:39 ` bugzilla-gcc at thewrittenword dot com 2021-07-19 21:00 ` me at larbob dot org 2021-07-19 22:43 ` me at larbob dot org 2021-07-20 16:06 ` me at larbob dot org 2021-07-20 16:07 ` me at larbob dot org 2021-07-20 16:08 ` me at larbob dot org 2021-07-20 17:04 ` dave.anglin at bell dot net 2021-07-20 17:05 ` me at larbob dot org 2021-07-20 17:58 ` me at larbob dot org 2021-07-20 18:24 ` me at larbob dot org 2021-07-20 23:58 ` me at larbob dot org 2021-07-21 0:01 ` me at larbob dot org 2021-07-21 2:32 ` bugzilla-gcc at thewrittenword dot com 2021-07-21 2:38 ` me at larbob dot org 2021-07-21 2:59 ` bugzilla-gcc at thewrittenword dot com 2021-07-21 4:36 ` bugzilla-gcc at thewrittenword dot com 2021-07-21 5:13 ` me at larbob dot org 2021-07-21 6:32 ` me at larbob dot org 2021-07-21 15:15 ` dave.anglin at bell dot net 2021-07-21 16:19 ` me at larbob dot org 2021-07-21 16:43 ` jvb at cyberscience dot com 2021-07-21 16:55 ` me at larbob dot org 2021-07-21 17:26 ` dave.anglin at bell dot net 2021-07-27 22:09 ` me at larbob dot org 2021-11-16 13:01 ` [Bug middle-end/61577] [9/10/11/12 " rguenth at gcc dot gnu.org 2022-05-27 9:35 ` [Bug middle-end/61577] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug middle-end/61577] [11/12/13/14 " rguenth 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-61577-4-Qv7k56CflK@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).