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 bootstrap/64919] bootstrap failure of gcc-4.9.2 on ia64-hpux in libgcc
Date: Mon, 27 Apr 2015 09:55:00 -0000	[thread overview]
Message-ID: <bug-64919-4-rRroYN4b3m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64919-4@http.gcc.gnu.org/bugzilla/>

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

John Buddery <jvb at cyberscience dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvb at cyberscience dot com

--- Comment #6 from John Buddery <jvb at cyberscience dot com> ---
I had this issue as well, and here is the solution I used in case anyone is
still interested. I believe it is caused by an HP-UX linker bug, the same one
described by this comment and workaround  in config/ia64/hpux.h:

  /* The HP-UX linker has a bug that causes calls from functions in
   .text.unlikely to functions in .text to cause a segfault.  Until
   it is fixed, prevent code from being put into .text.unlikely or
   .text.hot.  */

  #define TARGET_ASM_FUNCTION_SECTION ia64_hpux_function_section

While this workaround is sufficient for C code, unfortunately g++ can use
multiple text sections for various different reasons when compiling c++ code
(lookup Vague Linkage for details).

This means g++ is broken on HP ia64, and gcc 4.8.0 build using g++, which is
why the bootstrap now fails.

The workaround I applied was to add the line:

   #undef MAKE_DECL_ONE_ONLY

to gcc/config/ia64/hpux.h, below the lines I referenced above. This seems to
prevent gcc from using .linkonce.t sections, and keeps the HP-UX linker happy.
I've no idea if this is the correct solution, but it does produce a working
g++.

Unfortunately just applying this edit you your 4.9.2 sources and building isn't
good enough, because it's your existing broken g++ which does the stage1 build. 

As far as I can tell all g++ versions available for download are broken, so you
have to first download and build 4.7.4 or earlier, applying the same 
gcc/config/ia64/hpux.h as above. This version builds with gcc, not g++, so the
bootstrap isn't a problem. Once you have a fixed 4.7.4 g++, you can then use
that to bootstrap 4.9.2 - after again apply the hpux.h edit to the 4.9.2
sources.

In my case when building 4.9.2 I also had to disable libgomp, but I think
that's a different issue.

Of course a much better solution to all this would be to get a fixed HP linker;
but I can't even tell if any of the HP patches help as they don't seem to make
these fixes generally available.


  parent reply	other threads:[~2015-04-27  9:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-64919-4@http.gcc.gnu.org/bugzilla/>
2015-02-03 13:48 ` tgard at opentext dot com
2015-04-27  9:55 ` jvb at cyberscience dot com [this message]
2015-07-27  4:20 ` alm at sibmail dot ru
2015-07-27  4:44 ` alm at sibmail dot ru
2015-07-27 10:01 ` jvb at cyberscience dot com
2015-07-29  4:23 ` alm at sibmail dot ru
2015-10-19 16:46 ` josephpattara at gmail dot com
2015-10-20  5:35 ` alm at sibmail dot ru
2015-10-20 15:35 ` josephpattara at gmail dot com
2015-10-20 15:51 ` jvb at cyberscience dot com
2021-04-16 21:30 ` pinskia 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-64919-4-rRroYN4b3m@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).