public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: law@redhat.com
To: vmakarov@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/3589: GCC 3.0-CVS illegal instruction on hppa1.1-proelf
Date: Tue, 26 Mar 2002 20:06:00 -0000	[thread overview]
Message-ID: <20020327040602.10672.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/3589; it has been noted by GNATS.

From: law@redhat.com
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Joel Sherrill <joel.sherrill@OARcorp.com>, gcc-gnats@gcc.gnu.org,
        gcc-patches@gcc.gnu.org, vmakarov@gcc.gnu.org, joel@gcc.gnu.org,
        gcc-bugs@gcc.gnu.org
Subject: Re: bootstrap/3589: GCC 3.0-CVS illegal instruction on hppa1.1-proelf 
Date: Tue, 26 Mar 2002 20:59:08 -0700

  In message <3CA0F363.6A938C38@redhat.com>, Vladimir Makarov writes:
  > It is hard to achieve.  Of course the used object file format is major. 
  > So we could define __elfobj__ in pro-end.h and rtems.h.  But they are
  > connected with elf only config.gcc.  Somebody could create
  > hppa1.1-*-prosom using pro-end.h.  Of course it is stupid because there
  > is only proelf.
  > 
  > So I think the following patch is still reasonable.
  > 
  > 2002-03-26  Vladimir Makarov  <vmakarov@redhat.com>
  > 
  >         * pa/pa-pro-end.h (CPP_PREDEFINES): Add -D__pro__.
  > 
  >         * pa/lib2funcs.asm: Don't use .SPACE and .SUBSPACE if __pro__
  >         or __rtems_ is defined.
 I went ahead and installed this patch.
 
 Thanks,
 jeff
 


             reply	other threads:[~2002-03-27  4:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 20:06 law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-24  9:11 joel
2002-04-01 14:54 vmakarov
2002-03-28 13:46 John David Anglin
2002-03-28 12:56 Vladimir Makarov
2002-03-27 10:56 Vladimir Makarov
2002-03-26 14:26 Joel Sherrill
2002-03-26 14:26 Vladimir Makarov
2002-03-26 13:36 Joel Sherrill
2002-03-26 13:16 Vladimir Makarov
2002-03-26 13:06 Joel Sherrill
2002-03-26 12:56 Vladimir Makarov
2002-03-26 10:16 Joel Sherrill
2002-03-26  9:56 Vladimir Makarov
2002-03-26  9:56 law
2002-03-26  9:36 Vladimir Makarov
2002-03-26  9:26 Joel Sherrill
2002-03-26  9:16 Vladimir Makarov
2002-03-26  6:26 Joel Sherrill
2002-03-25 10:26 Vladimir Makarov
2002-03-25 10:16 law
2002-03-25  8:26 Vladimir Makarov
2002-03-22  9:41 vmakarov
2001-07-06  6:46 joel

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=20020327040602.10672.qmail@sources.redhat.com \
    --to=law@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=vmakarov@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).