public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvb at cyberscience dot com" <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: Wed, 09 Jun 2021 10:12:22 +0000 [thread overview] Message-ID: <bug-61577-4-mYL3XFxiaa@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 #228 from John Buddery <jvb at cyberscience dot com> --- Sorry it took a while, I've been away for a bit and have lots to catch up on. These patches are for 11.1.0, but should work on earlier versions too. With this I have a working gcc which I've tested on several large projects. Most of the patch is a cumulation of the patches posted earlier in this thread - unsigned pointer extension, reverting @gprel changes etc. gcov-tool.c avoids build errors from ftwbuf differences on HP, apply if you hit errors but may need tidying up. ia64.md is the patch for long calls, to avoid the 25 bit limit which prevents linking gcc. It's still a work in progress as the instruction bundling is wrong, but it does work. Note that you must apply the binutils patch (or build the current binutils master, or a release after 2.36) to get an assembler that will work with brl and the HP linker. Do not apply the ia64.md patch without building a patched gnu assembler first! Also note that you need a working C++ compiler to bootstrap. That sounds obvious, but is harder than you think - as far as I know, none of the distributed g++ versions work sufficiently. One way to get a working 4.9.2 g++ is described in my post in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64919 but there may be other solutions as well. I've never tried to bootstrap with aCC. My configure command is: ../gcc-11.1.0/configure --enable-comdat --disable-libgomp --with -as=/usr/local/binutils/bin/as --enable-languages=c,c++ --prefix=/usr/local/gcc- 11.1.0 --with-gmp=/usr/local_32 --with-mpc=/usr/local_32 --with-mpfr=/usr/local_ 32 --with-dwarf2 The --enable-comdat I think is required. I think libgomp doesn't build, I've never investigated though and disable it. I use dwarf2 as recent gdb versions won't work. The assembler I use is a patched binutils 2.36. Good luck!
next prev parent reply other threads:[~2021-06-09 10:12 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 [this message] 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 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-mYL3XFxiaa@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).