Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!ogicse!intelhf!ichips!iwarp.intel.com!inews!nevin!bhoughto
From: bhoughto@nevin.intel.com (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: increment casted void pointer  --  ANSI?
Message-ID: <3649@inews.intel.com>
Date: 4 Apr 91 05:18:18 GMT
References: <15619@smoke.brl.mil> <718q01zZ4fNC00@amdahl.uts.amdahl.com> <15675@smoke.brl.mil>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 22

In article <15675@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>environments.  (While we were able to imagine an environment where
>floating and integral types were maintained in separate address
>spaces, I don't know of any actual implementations like that.)

Is it okay to propose one?

Someone over in comp.<mumble> (I think comp.unix.internals>
mentioned that the i860(tm) has one set of registers for
integers and one for floating-point.  (In fact, any
architecture involving separate CPU and FPU would be that
way, but the i860(tm) does them both on the same chip,
bringing up issues of further transparency by eliminating
the need for external memory or bus operations to implement
a FPU-to-CPU (floating to int) transfer.)

If for some reason the compiler decided that the union should
be handled entirely in register space, the ints and floats
would indeed have different locations.

				--Blair
				  "Yeah, I could beat up Mike Tyson."