From: Jeffrey A Law <law@cygnus.com>
To: mrs@wrs.com (Mike Stump)
Cc: mark@markmitchell.com, egcs@cygnus.com
Subject: Re: Alias code
Date: Wed, 01 Jul 1998 00:54:00 -0000 [thread overview]
Message-ID: <19341.899255740@hurl.cygnus.com> (raw)
In-Reply-To: <199807010045.RAA12576@kankakee.wrs.com>
In message < 199807010045.RAA12576@kankakee.wrs.com >you write:
> > Date: Mon, 29 Jun 1998 04:18:30 -0600
> > From: Jeffrey A Law <law@cygnus.com>
>
> > 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.
>
> > Thoughts?
>
> Sigh, not sure what to say other than it would be nice if someone
> worked to get major api type things like this that are simple into
> gcc2. Then all code can do it, and we'd have fewer problems.
That still wouldn't resolve how to deal with ports and front-ends
that aren't in the gcc2 or egcs source trees.
jeff
next prev parent reply other threads:[~1998-07-01 0:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-30 19:49 Mike Stump
1998-07-01 0:54 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-06-29 22:34 Franz Sirl
1998-06-30 11:53 ` David Edelsohn
[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=19341.899255740@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mark@markmitchell.com \
--cc=mrs@wrs.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).