This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Unicode mangling (was Re: [PATCH] Java: New C++ ABI compatibility changes.)


Gavin> Also, while I'm talking, I'll venture into an area I'm less
Gavin> confident about.  It seems to me we can't use UTF8 as an
Gavin> encoding from gcc to the assembler unless the assembler allows
Gavin> any 8bit character in identifiers (which seems unlikely).

We actually only need a weaker constraint, namely that the assembler
will allow any byte with the 8th bit set.  Maybe that is what you
meant -- it is unclear to me.

The way UTF-8 is designed, ordinary ascii (8th bit clear) bytes always
represent themselves (as characters).  A multi-byte character will
never include a byte with the 8th bit clear.  So you don't have to
worry about the assembler seeing \0 or anything like that.

Tom

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]