[LLVMdev] [llvm-commits] [cfe-commits] [PATCH] [llvm+clang] memset for non-8-bit bytes

Patrik Hägglund H patrik.h.hagglund at ericsson.com
Fri Oct 19 11:43:35 PDT 2012

> I'm a bit confused by this concept. 

For the term byte, I use the "archaic" definition in the C (and C++) standard (section 3.6):

  addressable unit of data storage large enough to hold any member of the basic character
  set of the execution environment

/Patrik Hägglund 

-----Original Message-----
From: Jakob Stoklund Olesen [mailto:stoklund at 2pi.dk] 
Sent: den 19 oktober 2012 18:28
To: Patrik Hägglund H
Cc: Chris Lattner; llvmdev at cs.uiuc.edu
Subject: Re: [llvm-commits] [cfe-commits] [PATCH] [llvm+clang] memset for non-8-bit bytes

On Oct 19, 2012, at 2:24 AM, Patrik Hägglund H <patrik.h.hagglund at ericsson.com> wrote:

>> non-8-bit byte 

I'm a bit confused by this concept. I'm aware of the archaic meaning of the word byte, but it has meant 8 bits for the last 30 years. There's even an ISO/IEC standard.

I know of architectures like Texas' C55x DSPs that address 16 bits at a time, but even their data sheets state:

. 256K Bytes Zero-Wait State On-Chip RAM, Composed of:
  . -  64K Bytes of Dual-Access RAM (DARAM), 8 Blocks of 4K x 16-Bit
  . -  192K Bytes of Single-Access RAM (SARAM), 24 Blocks of 4K x 16-Bit

Perhaps you could begin by defining more accurately what you're talking about?


More information about the llvm-dev mailing list