From: coypu@sdf.org
To: gcc@gcc.gnu.org
Cc: port-vax@netbsd.org
Subject: syncing the GCC vax port
Date: Sat, 30 Mar 2019 09:03:00 -0000 [thread overview]
Message-ID: <20190330090306.GA29299@SDF.ORG> (raw)
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.
As an initial step, I need to sync the source code.
netbsd/vax has some outstanding work on GCC.
I've done this, and I can run programs built by this compiler:
http://coypu.sdf.org/gcc-9-vax.diff
(My tree has more detail on the changes done:
https://github.com/gcc-mirror/gcc/compare/master...coypoop:vax )
Matt Thomas (the GCC VAX maintainer) is the author of most of these
changes, I suspect he will not be very responsive by email.
Not being the author, I might not be able to answer all the questions,
but I can try my best.
How do I get this across? comments? straight to gcc-patches? :-)
I know Jeff Law did not like the change to builtins.md as being wrong. I
can omit them, I forgot about it until typing this email :)
caveat: had an ICE during reload in the build process, I hid it
under the rug with -O0.
next reply other threads:[~2019-03-30 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 9:03 coypu [this message]
2019-03-31 17:26 ` Paul Koning
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=20190330090306.GA29299@SDF.ORG \
--to=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).