https://sourceware.org/bugzilla/show_bug.cgi?id=32211
--- Comment #8 from Dan McDonald <danmcd at mnx dot io> --- Nope. -w was intentional. it's the v8dbg_SmiTag symbol that's getting set to 0 and getting ignored. The v8dbg_SmiTagMask is set to 0x1 and is not. Something changed between 2.40 and 2.41 as far as I can tell; perhaps you should inspect diffs between those two releases to see what happened. I save the entire output on the large .a files, and here's what I see on 2.40 and earlier... Disassembly of section .data.v8dbg_SmiTagMask: 00000000 <v8dbg_SmiTagMask>: 0: 01 00 add %eax,(%eax) 2: 00 00 add %al,(%eax) Disassembly of section .bss.v8dbg_SmiTag: 00000000 <v8dbg_SmiTag>: 0: 00 00 add %al,(%eax) 2: 00 00 add %al,(%eax) Disassembly of section .data.v8dbg_HeapObjectTagMask: 00000000 <v8dbg_HeapObjectTagMask>: 0: 03 00 add (%eax),%eax 2: 00 00 add %al,(%eax) And here's what I see on 2.41 and later... Disassembly of section .data.v8dbg_SmiTagMask: 00000000 <v8dbg_SmiTagMask>: 0: 01 00 add %eax,(%eax) 2: 00 00 add %al,(%eax) Disassembly of section .data.v8dbg_HeapObjectTagMask: 00000000 <v8dbg_HeapObjectTagMask>: 0: 03 00 add (%eax),%eax 2: 00 00 add %al,(%eax) v8dbg_SmiTagMask is getting dropped, and so are all other values set to 0. -- You are receiving this mail because: You are on the CC list for the bug.
