public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Michael P. Hayes" <michaelh@ongaonga.chch.cri.nz>
To: law@cygnus.com
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
	mark@markmitchell.com, egcs@cygnus.com
Subject: Re: Alias code
Date: Tue, 30 Jun 1998 04:50:00 -0000	[thread overview]
Message-ID: <199806301022.KAA20139@ongaonga.chch.cri.nz> (raw)
In-Reply-To: <13707.899141795@hurl.cygnus.com>

Jeffrey A Law writes:

 > However, there are still backends which we can not convert because they
 > are not part of egcs (for example the tic30/c40 ports which Michael
 > Hayes is working on) or front-ends which we can't convert yet (Pascal,
 > Ada, Modula3 immediately come to mind).  Thus we have to avoid breaking
 > those hunks of code with the alias set changes.

Don't worry about breaking the C30/C40 port.  There's not much left to do
to slot it into EGCS.  There are some more important patches for reorg
that I've got to submit to get things up and running with EGCS.

While on the alias code subject, EGCS could do with a mechanism so
that a programmer can hint to the compiler that a memory reference is
to a different address space, say an internal memory block.  The
backend could then do a better scheduling job by knowing that the
memory access is likely to be faster than normal and that it won't
conflict with an external memory access.  Any ideas?

Michael.




  reply	other threads:[~1998-06-30  4:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199806291730.KAA16121@cygnus.com>
1998-06-29 20:41 ` Jeffrey A Law
1998-06-30  4:50   ` Michael P. Hayes [this message]
1998-06-30 14:46     ` Joern Rennecke
1998-07-01  0:54       ` Michael P. Hayes
1998-07-02  1:39         ` Alias code - how does the SHARC do it Alan Lehotsky
1998-07-03  1:51           ` Michael P. Hayes
1998-07-03 12:21             ` Alan Lehotsky
1998-06-30 19:49 Alias code Mike Stump
1998-07-01  0:54 ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1998-06-29 22:34 Franz Sirl
1998-06-30 11:53 ` David Edelsohn
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=199806301022.KAA20139@ongaonga.chch.cri.nz \
    --to=michaelh@ongaonga.chch.cri.nz \
    --cc=Franz.Sirl-kernel@lauterbach.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).