Re: does graphite affect the c++ munging? Does -On?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "JW" == Jonathan Wakely <jwakely.gcc@xxxxxxxxx> writes:

JW> It doesn't match, c++filt shows that symbol is

Ah, thanks.  I'll check out c++filt.

JW> icu::LEFontInstance::mapCharsToGlyphs(char16_t const*, int, int,
JW> signed char, icu::LECharMapper const*, signed char,
JW> icu::LEGlyphStorage&) const

JW> char16_t is not unsigned short.

OK.

That said:

  :; g++ -march=amdfam10 -dM -E  - </dev/null | grep CHAR16
  #define __CHAR16_TYPE__ short unsigned int
  #define __GCC_ATOMIC_CHAR16_T_LOCK_FREE 2

Where should I look for why, given __CHAR16_TYPE__ is short unsigned int,
the compile of icu munges differently than the consumer of icu munges?

-JimC
-- 
James Cloos <cloos@xxxxxxxxxxx>         OpenPGP: 1024D/ED7DAEA6


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux