Re: Supporting byte-addressability on word-addressed hardware

mfx@cs.tu-berlin.de (Markus Freericks)
Thu, 6 Jul 1995 14:10:40 GMT

          From comp.compilers

Related articles
Supporting byte-addressability on word-addressed hardware lehotsky@tiac.net (1995-06-27)
Re: Supporting byte-addressability on word-addressed hardware simmons@bnr.ca (steve (s.s.) simmons) (1995-06-28)
Re: Supporting byte-addressability on word-addressed hardware markt@harlequin.co.uk (1995-07-04)
Re: Supporting byte-addressability on word-addressed hardware pardo@cs.washington.edu (1995-07-05)
Re: Supporting byte-addressability on word-addressed hardware bob@tera.com (1995-07-06)
Re: Supporting byte-addressability on word-addressed hardware mfx@cs.tu-berlin.de (1995-07-06)
Re: Supporting byte-addressability on word-addressed hardware tl@ae.chalmers.se (1995-07-12)
Re: Supporting byte-addressability on word-addressed hardware pardo@cs.washington.edu (1995-07-19)
Re: Supporting byte-addressability on word-addressed hardware meissner@cygnus.com (Michael Meissner) (1995-07-20)
| List of all articles for this month |

Newsgroups: gnu.gcc.help,comp.compilers
From: mfx@cs.tu-berlin.de (Markus Freericks)
Keywords: architecture, design
Organization: TU Berlin Fachbereich Informatik
References: 95-06-081 95-07-049
Date: Thu, 6 Jul 1995 14:10:40 GMT

markt@harlequin.co.uk (Mark Tillotson) writes:
> lehotsky@tiac.net (Alan Lehotsky) wrote:
> > I'm beginning a project to modify a gcc port to a machine that only
> > support 32-bit word addressed memory. At present, the port treats
> > ints, shorts and chars as the same size objects.
>
> Is this current scheme actually a problem??? How much space really is
> wasted? Is it significant? Is speed or size more important anyhow?


Depends very much on the applications you compile, of course. Typical
numerical code should not be affected very much, but just imagine compiling
a text editor with such a compiler --- using up four times the necessary
space could be seen as a mis-feature. (You might want to treat arrays
specially, but with C this doesn't work so well, since you can't know
whether your pointer points to an ordinary char (=long) or to a "packed"
char (=a byte). You might want to introduce pointer descriptors to
work around this... that way lies madness ;-)


[..]


-- Markus
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.