From: Sid Maxwell <srmaxwell3@gmail.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Julian Brown <julian@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: I have questions regarding the 4.3 codebase...
Date: Thu, 23 Mar 2023 10:32:00 -0400 [thread overview]
Message-ID: <CAGx9W7gP0pQKQY6HvoQat_Nj8fK0yLy=DezoN0xv6YeZ445W-g@mail.gmail.com> (raw)
In-Reply-To: <AF0CBF0D-22CF-4136-BB03-0321FBE02D86@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
I'll take a look, Paul, thanks. It hadn't occurred to me to compare
different machines' uses.
-+- Sid
On Thu, Mar 23, 2023 at 10:29 AM Paul Koning <paulkoning@comcast.net> wrote:
>
>
> > On Mar 23, 2023, at 10:13 AM, Sid Maxwell via Gcc <gcc@gcc.gnu.org>
> wrote:
> >
> > Thanks for reaching out, Julian, I greatly appreciate your help. Please
> > forgive and over- or under-sharing. If I've left something out, please
> let
> > me know.
> >
> > From my pdp10.md:
> >
> > ;; JIRA sw_gcc-68. gcc recognizes the "movmemhi" 'instruction' for
> > ;; doing block moves, as in struct assignment. This pattern wasn't
> > ;; present, however. I've added it, and it's companion function
> > ;; pdp10_expand_movmemhi().
> >
> > (define_expand "movmemhi"
> > [(match_operand:BLK 0 "general_operand" "=r")
> > (match_operand:BLK 1 "general_operand" "=r")
> > (match_operand:SI 2 "general_operand" "=r")
> > (match_operand:SI 3 "const_int_operand" "")
> > ]...
>
> I don't remember that far back, but looking at current examples (like
> vax.md) that seems like an odd pattern. vax.md has a three operand pattern
> with the first two marked as "memory_operand" and only the first one has
> the = modifier on it showing it's an output operand.
>
> What does the 4.3 version of gccint say about it? Or the 4.3 version of
> vax.md?
>
> paul
>
>
prev parent reply other threads:[~2023-03-23 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 22:27 Sid Maxwell
2023-03-23 7:08 ` Julian Brown
2023-03-23 14:13 ` Sid Maxwell
2023-03-23 14:29 ` Paul Koning
2023-03-23 14:32 ` Sid Maxwell [this message]
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='CAGx9W7gP0pQKQY6HvoQat_Nj8fK0yLy=DezoN0xv6YeZ445W-g@mail.gmail.com' \
--to=srmaxwell3@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=julian@codesourcery.com \
--cc=paulkoning@comcast.net \
/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).