From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: law@cygnus.com
Cc: mark@markmitchell.com, egcs@cygnus.com, egcs-patches@cygnus.com
Subject: Re: Alias code
Date: Mon, 29 Jun 1998 22:34:00 -0000 [thread overview]
Message-ID: <98062921350100.05397@ns1102.munich.netsurf.de> (raw)
Am Mon, 29 Jun 1998 schrieb Jeffrey A Law:
>In message <199806291730.KAA16121@cygnus.com>you write:
> > At 12:18 29.06.98 , Jeffrey A Law wrote:
> > >
> > >We've got a little problem.
> > >
> > >While the machine independent code is mostly free of gen_rtx (MEM)
> > >calls, many of the target files, and some of the front-ends that we
> > >want to interoperate (but possibly do not control) with are not free
> > >of such calls.
> >
> > Jeff, if you want to see that changed everywhere, why don't you simply put
> > a request for patches on the list like for the warning patches? The changes
> > are very simple (I even remember sending you a sed script doing most of the
> > work), so nearly everyone can do it.
>Folks should certainly feel free to submit these changes. I certainly
>would like to see this fixed throughout the compiler. Posting the
>sed script again would probably encourage this :-)
So here is this supersimple script again ;-). I've done it for the rs6000
backend and it catches most gen_rtx in there. Only the gen_rtx(GET_CODE...)
cases are missing, since I don't know what to do there. Eventually people
without FSF assignement like me have to split the patches into more parts to
avoid the assignement.
Franz.
#!/bin/sh
sed -e "s/gen_rtx (COMPARE, /gen_rtx_COMPARE (/" <$1 |\
sed -e "s/gen_rtx (MEM, /gen_rtx_MEM (/" |\
sed -e "s/gen_rtx (REG, /gen_rtx_REG (/" |\
sed -e "s/gen_rtx (PLUS, /gen_rtx_PLUS (/" |\
sed -e "s/gen_rtx (USE, /gen_rtx_USE (/" |\
sed -e "s/gen_rtx (SYMBOL_REF, /gen_rtx_SYMBOL_REF (/" |\
sed -e "s/gen_rtx (EXPR_LIST, /gen_rtx_EXPR_LIST (/" |\
sed -e "s/gen_rtx (IF_THEN_ELSE, /gen_rtx_IF_THEN_ELSE (/" |\
sed -e "s/gen_rtx (SET, /gen_rtx_SET (/" |\
sed -e "s/gen_rtx (PARALLEL, /gen_rtx_PARALLEL (/" |\
sed -e "s/gen_rtx (NE, /gen_rtx_NE (/" |\
sed -e "s/gen_rtx (LABEL_REF, /gen_rtx_LABEL_REF (/" |\
sed -e "s/gen_rtx (CONST_INT, /gen_rtx_CONST_INT (/" |\
sed -e "s/gen_rtx (SUBREG, /gen_rtx_SUBREG (/" |\
sed -e "s/gen_rtx (INSN_LIST, /gen_rtx_INSN_LIST (/" |\
sed -e "s/gen_rtx (CLOBBER, /gen_rtx_CLOBBER (/" |\
sed -e "s/gen_rtx (SCRATCH, /gen_rtx_SCRATCH (/" |\
sed -e "s/gen_rtx.(LO_SUM,./gen_rtx_LO_SUM (/" >$1.new
next reply other threads:[~1998-06-29 22:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-29 22:34 Franz Sirl [this message]
1998-06-30 11:53 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
1998-06-30 19:49 Mike Stump
1998-07-01 0:54 ` Jeffrey A Law
[not found] <199806291730.KAA16121@cygnus.com>
1998-06-29 20:41 ` Jeffrey A Law
1998-06-30 4:50 ` Michael P. Hayes
1998-06-30 14:46 ` Joern Rennecke
1998-07-01 0:54 ` Michael P. Hayes
1998-06-29 19:43 Michael Meissner
1998-06-29 3:22 Jeffrey A Law
1998-06-29 11:08 ` Mark Mitchell
1998-06-29 22:34 ` Jeffrey A Law
1998-06-29 11:08 ` Mark Mitchell
1998-06-29 19:43 ` Jeffrey A Law
1998-06-29 14:05 ` Franz Sirl
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=98062921350100.05397@ns1102.munich.netsurf.de \
--to=franz.sirl-kernel@lauterbach.com \
--cc=egcs-patches@cygnus.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=mark@markmitchell.com \
/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).