public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje@cup.hp.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/10229] [3.3/3.4 regression] [IA-64 HP-UX 11.22] Internal compiler error in emit_move_insn
Date: Mon, 09 Jun 2003 22:24:00 -0000	[thread overview]
Message-ID: <20030609222456.1784.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030326193600.10229.gcc-bug@bullseye.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10229



------- Additional Comments From sje@cup.hp.com  2003-06-09 22:24 -------
Subject: Re:  [3.3/3.4 regression] [IA-64 HP-UX 11.22] Internal compiler error in emit_move_insn

There are two bugs here, one is that the test case you sent will not
compile, and this is because of the use of __builtin_ia64_bsp.  The
second bug is that a build/bootstrap of GCC should not be compiling
unwind-ia64.c.

In GCC 3.3, the issue of compiling unwind-ia64.c is fixed and
unwind-ia64.c is not compiled.  When I configure GCC for
ia64-hp-hpux11.22, I specify --enable-libunwind-exceptions to use the HP
unwind library when building the ia64-hp-hpux11.22 GCC.  The GCC unwind
part of libgcc (unwind-ia64.c) has never been properly ported to HP-UX
and probably wouldn't work even if it compiled.  With GCC 3.3 and later
it shouldn't try to compile it.

In terms of the small test case, the problem is that __builtin_ia64_bsp
doesn't work properly with ILP32 mode.  It could be fixed but the only
use of it is in the unwind library (which we don't use) so I am not too
excited about fixing it.  Note that fixing the bug in the test case
(making it compile) would not necessarily make the code in unwind-ia64.c
work, it would probably need more changes to work properly on HP-UX.

While working on the GCC port to HP-UX IA64 we made a decision to use
the HP-UX unwind library instead of porting the GCC one in order to
maximize the compatibility between the HP-UX compilers and GCC, that is
why we never dealt with this issue.

Also, I don't think GCC 3.2.2 works properly on ia64-hp-hpux11.22.  Most
of it is there, but it might have other problems.  I would use GCC 3.3
along with one patch I submitted after release, See
http://gcc.gnu.org/ml/gcc-patches/2003-05/msg01937.html for the patch I
submitted and checked in on the main line and on the GCC 3.3 branch.

Steve Ellcey
sje@cup.hp.com


  parent reply	other threads:[~2003-06-09 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030326193600.10229.gcc-bug@bullseye.com>
2003-06-02 19:47 ` dhazeghi@yahoo.com
2003-06-08  4:08 ` dhazeghi@yahoo.com
2003-06-08 18:57 ` pinskia@physics.uc.edu
2003-06-09 22:24 ` sje@cup.hp.com [this message]
2003-06-11 15:51 ` dhazeghi@yahoo.com

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=20030609222456.1784.qmail@sources.redhat.com \
    --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).