Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!aglew
From: aglew@ccvaxa.UUCP
Newsgroups: comp.arch
Subject: Re: RISC data alignment
Message-ID: <28200102@ccvaxa>
Date: 19 Feb 88 17:27:00 GMT
References: <2710@mmintl.UUCP>
Lines: 14
Nf-ID: #R:mmintl.UUCP:2710:ccvaxa:28200102:000:680
Nf-From: ccvaxa.UUCP!aglew    Feb 19 11:27:00 1988


>It would be more correct if a one byte pad were explicity put in after
>the "char t_txt", but I think my point is still valid.  There are some
>cases where the order of the structure elements cannot be changed.
>
>Mike Mitchell	{decvax,seismo,ihnp4,philabs}!mcnc!rti!mcm  mcm@rti.rti.org

Agreed. I've written code that has to deal with hardware data structures
like PTEs. Rearranging data structures is an optimization I would like
to be able to turn on, but would definitely want to be able to turn off.

And, yes, if the compiler guys can make the compiler automatically discover
which those are, I'll use automatic generation - but until then I would
like automatic control.