Displaying 6 results from an estimated 6 matches for "0x00ab".
Did you mean:
0x00a0
2003 Aug 29
1
RC2: Compile errors Solaris 8 (cc) and suggested fix
...- 0x00F4,
- 0x00F6,
- 0x00F2,
- 0x00FB,
- 0x00F9,
- 0x00FF,
- 0x00D6,
- 0x00DC,
- 0x00A2,
- 0x00A3,
- 0x00A5,
- 0x20A7,
- 0x0192,
- 0x00E1,
- 0x00ED,
- 0x00F3,
- 0x00FA,
- 0x00F1,
- 0x00D1,
- 0x00AA,
- 0x00BA,
- 0x00BF,
- 0x2310,
- 0x00AC,
- 0x00BD,
- 0x00BC,
- 0x00A1,
- 0x00AB,
- 0x00BB,
- 0x2591,
- 0x2592,
- 0x2593,
- 0x2502,
- 0x2524,
- 0x2561,
- 0x2562,
- 0x2556,
- 0x2555,
- 0x2563,
- 0x2551,
- 0x2557,
- 0x255D,
- 0x255C,
- 0x255B,
- 0x2510,
- 0x2514,
- 0x2534,
- 0x252C,
- 0x251C,
- 0x2500,
- 0x253C,
- 0x255E,
- 0x255F,
- 0x255A,
- 0x2554,
-...
2016 May 07
2
Debug info scope of explicit casting type does not seem correct
...* // f1
0x00000087: DW_TAG_template_type_parameter [6]
0x0000008e: DW_TAG_lexical_block [7] *
0x0000009f: DW_TAG_variable [8]
0x000000ab: DW_TAG_pointer_type [9] // foo*
& in fact, if you introduce another template that's similar to f1, its variable's type is 0x00ab - so it points into f1's children. Seems GCC puts it in whatever scope first references the pointer type.
I think it's probably as sensible, and a bit simpler, to put any such basic types in the CU scope.
(granted, if GCC and Clang were really smart, the pointer type in f1 could be po...
2016 Apr 30
2
Debug info scope of explicit casting type does not seem correct
Hi,
I am wondering if this behavior of creating debug info is correct.
A type in compile unit entry is pointing to a type under subprogram entry?!
This is the root cause of https://llvm.org/bugs/show_bug.cgi?id=27579
0x0000000b: DW_TAG_compile_unit [1] *
0x00000026: DW_TAG_pointer_type [2]
DW_AT_type [DW_FORM_ref4] (cu + 0x002c => {0x0000002c})
2016 May 08
2
Debug info scope of explicit casting type does not seem correct
...* // f1
0x00000087: DW_TAG_template_type_parameter [6]
0x0000008e: DW_TAG_lexical_block [7] *
0x0000009f: DW_TAG_variable [8]
0x000000ab: DW_TAG_pointer_type [9] // foo*
& in fact, if you introduce another template that's similar to f1, its variable's type is 0x00ab - so it points into f1's children. Seems GCC puts it in whatever scope first references the pointer type.
I think it's probably as sensible, and a bit simpler, to put any such basic types in the CU scope.
(granted, if GCC and Clang were really smart, the pointer type in f1 could be po...
2003 Dec 01
0
No subject
...F 0x009F # <control>
0xA0 0x00A0 # NO-BREAK SPACE
0xA2 0x00A2 #
CENT SIGN
0xA3 0x00A3 # POUND SIGN
0xA4 0x00A4 # CURRENCY SIGN
0xA5 0x00A5 #
YEN SIGN
0xA6 0x00A6 # BROKEN BAR
0xA7 0x00A7 # SECTION SIGN
0xA8 0x00A8 #
DIAERESIS
0xA9 0x00A9 # COPYRIGHT SIGN
0xAA 0x00D7 # MULTIPLICATION SIGN
0xAB
0x00AB # LEFT-POINTING DOUBLE ANGLE QUOTATION MARK
0xAC 0x00AC # NOT SIGN
0xAD
0x00AD # SOFT HYPHEN
0xAE 0x00AE # REGISTERED SIGN
0xAF 0x00AF # MACRON
0xB0
0x00B0 # DEGREE SIGN
0xB1 0x00B1 # PLUS-MINUS SIGN
0xB2 0x00B2 # SUPERSCRIPT
TWO
0xB3 0x00B3 # SUPERSCRIPT THREE
0xB4 0x00B4 # ACUTE ACCENT
0xB5 0x00B...
2003 Dec 01
0
No subject
...00A4 # CURRENCY SIGN
> 0xA5 0x00A5 # YEN SIGN
> 0xA6 0x00A6 # BROKEN BAR
> 0xA7 0x00A7 # SECTION SIGN
> 0xA8 0x00A8 # DIAERESIS
> 0xA9 0x00A9 # COPYRIGHT SIGN
> 0xAA 0x00AA # FEMININE ORDINAL INDICATOR
> 0xAB 0x00AB # LEFT-POINTING DOUBLE ANGLE QUOTATION MARK
> 0xAC 0x20AC # EURO
> 0xAD 0x00AD # SOFT HYPHEN
> 0xAE 0x00AE # REGISTERED SIGN
> 0xAF 0x00AF # MACRON
> 0xB0 0x00B0 # DEGREE SIGN
> 0xB1 0x00B1 # PLUS-MINUS SIGN
> 0...