Related articles |
---|
Re: Help: How to determine big/little endian? doconnor@sedona.intel.com (1995-08-17) |
Re: Help: How to determine big/little endian? ECE@dwaf-hri.pwv.gov.za (John Carter) (1995-08-21) |
Re: Help: How to determine big/little endian? baynes@ukpsshp1.serigate.philips.nl (1995-08-21) |
Re: Help: How to determine big/little endian? pardo@cs.washington.edu (1995-08-21) |
Re: Help: How to determine big/little endian? mw@ipx2.rz.uni-mannheim.de (1995-08-22) |
Re: Help: How to determine big/little endian? tonyk@cybercom.net (1995-08-22) |
Re: Help: How to determine big/little endian? paysan@informatik.tu-muenchen.de (1995-08-21) |
[11 later articles] |
Newsgroups: | comp.arch,comp.compilers |
From: | doconnor@sedona.intel.com (Dennis O'Connor -FT-~) |
Keywords: | C, architecture, comment |
Organization: | Intel Corporation, Chandler, AZ |
References: | <4074ig$nh7@masala.cc.uh.edu> <CLIFFC.95Aug10172002@crocus.hpl.hp.com> |
Date: | Thu, 17 Aug 1995 03:26:05 GMT |
If the C standard specified a flag or pair of flags that the
compiler would set to indicate whether the target architecture
was big- or little-endian, that would be a big help.
So, how about it, GNU and ANSI ? Let's see __BIGEND__
and __LITTLEEND__ incorporated into the standards.
Thanks.
--
Dennis O'Connor doconnor@sedona.intel.com
i960(R) Architecture and Core Design
[How often in otherwise platform independent code do you really need to know
the byte order? I've almost always been able to program around it without
much trouble. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.