public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gcc-patches@gcc.gnu.org
Cc: gcc@gcc.gnu.org, msokolov@ivan.harhan.org
Subject: Re: FWIW: VAX fix backport and gcc built on 4.3BSD first time ever!
Date: Thu, 14 Dec 2000 17:22:00 -0000	[thread overview]
Message-ID: <200012150122.UAA24406@hiauly1.hia.nrc.ca> (raw)

> Hi there,
> 
> I know you guys don't want this in the 2.95.3 release, but I thought I would
> still post it for anybody who finds it useful. IMHO, this patch from the trunk
> from a while ago:
> 
> : Wed Aug 25 01:36:11 1999  John David Anglin  <dave@hiauly1.hia.nrc.ca>
> :
> :         * calls.c (emit_call_1): Use call_pop/call_value_pop for all values
> :         of n_popped when call/call_value are not defined.
> 
> really needs to be backported to the gcc-2_95-branch. Without this patch, gcc

I think this patch was actually from the gcc stream that Kenner was working
on.  I have a patched version of gcc-2.8.1 that works reasonably well under
VAX Ultrix 4.3.  It also has g++.  I was never able to successfully build
2.95 under Ultrix 4.3.  Congratulations!

Rather than back porting this patch, I think it would be better to get
the current mainline code working.  I am able to build the C language
sucessfully with gcc but there are still problems with a g++ stack
overflow building libstdc++.  There are a couple of patches pending
that enable one to get this far.  With the native cc, there are a whole
bunch of enum comparisons that still need to be fixed.  This is straight
forward but tedious.  You need a recent version of binutils.  This
fixes a long jmp problem that you will encounter building expr.c.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

             reply	other threads:[~2000-12-14 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-14 17:22 John David Anglin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-21 21:53 Michael Sokolov
2000-12-19 23:51 Michael Sokolov
     [not found] <no.id>
2000-12-19 21:48 ` John David Anglin
2000-12-21 14:32   ` John David Anglin
2000-12-19 21:22 John David Anglin
2000-12-19 18:40 Michael Sokolov
2000-12-14 12:44 Michael Sokolov
2000-12-19 18:01 ` Marc Espie

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=200012150122.UAA24406@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=msokolov@ivan.harhan.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).