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 Jul 2015 10:01:00 -0000	[thread overview]
Message-ID: <bug-64919-4-Xh4bSXdwAO@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

--- Comment #9 from John Buddery <jvb at cyberscience dot com> ---
I should clarify that the workaround above only works fully on 4.9.2 and
earlier.

>From 5.0 onwards, gcc seems to have a problem building 32 bit code for
ia64-hpux.
It doesn't emit intstructions to properly set the top two bits of pointers
after widening, which is required because of the way ia64 segments it's address
space.

So, you might have better luck with 4.9.2. Or, you might be able to build gcc
as a 64 bit executable (though I don't know how to do configure it this way).


  parent reply	other threads:[~2015-07-27 10:01 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
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 [this message]
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-Xh4bSXdwAO@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).