From: Paul Koning <paulkoning@comcast.net>
To: coypu@sdf.org
Cc: gcc@gcc.gnu.org, port-vax@netbsd.org
Subject: Re: syncing the GCC vax port
Date: Sun, 31 Mar 2019 17:26:00 -0000 [thread overview]
Message-ID: <7E381867-0CB2-4440-B773-66257A46AF22@comcast.net> (raw)
In-Reply-To: <20190330090306.GA29299@SDF.ORG>
> On Mar 30, 2019, at 5:03 AM, coypu@sdf.org wrote:
>
> hi folks,
>
> i was interesting in tackling some problems gcc netbsd/vax has.
> it has some ICEs which are in reload phase. searching around, the answer
> to that is "switch to LRA first". Now, I don't quite know what that is
> yet, but I know I need to try to do it.
That's not quite the whole story.
The answer is (1) switch from CC0 to CCmode condition code handling, which enables (2) switch from Reload to LRA.
(1) requires actual work, not terribly hard but not entirely trivial. (2) may take as little as switching the "use LRA" flag to "yes".
I did (1) as well as a tentative (2) for pdp11 last year. It was reasonably straightforward thanks to a pile of help from Eric Botcazou and his gcc wiki articles on the subject. You might find the pdp11 deltas for CCmode helpful as a source of ideas, since the two machines have a fair amount in common as far as condition codes goes. At least for the integer ops (pdp11 has separate floating point conditions, vax doesn't).
paul
next prev parent reply other threads:[~2019-03-31 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 9:03 coypu
2019-03-31 17:26 ` Paul Koning [this message]
2019-03-31 17:41 ` coypu
2019-04-01 15:33 ` Jeff Law
2019-04-29 20:08 ` Jeff Law
2019-09-20 11:15 ` coypu
2019-09-20 21:04 ` syncing the GCC vax port, atomic issue coypu
2019-09-20 21:45 ` Jeff Law
2019-09-20 22:08 ` coypu
2019-09-21 1:18 ` coypu
2019-09-21 18:27 ` Paul Koning
2019-10-01 19:44 ` Jeff Law
2019-10-01 19:43 ` Jeff Law
2019-10-02 9:39 ` Richard Earnshaw (lists)
2019-10-02 17:17 ` Segher Boessenkool
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=7E381867-0CB2-4440-B773-66257A46AF22@comcast.net \
--to=paulkoning@comcast.net \
--cc=coypu@sdf.org \
--cc=gcc@gcc.gnu.org \
--cc=port-vax@netbsd.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).