https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65028

--- Comment #51 from Martin Jambor <jamborm at gcc dot gnu.org> ---
So unless I made some mistake, we are looking a the following chain of
calls and aliases

main/48071 -> _ZN18eonImageCalculatorC1Ev/50391 ->alias->
_ZN18eonImageCalculatorC2Ev/50390 ->
->_ZN12ggPhotometerC1ERK10ggSpectrumS2_S2_S2_S2_S2_S2_/49466
->alias->_ZN12ggPhotometerC2ERK10ggSpectrumS2_S2_S2_S2_S2_S2_/49465 ->
-> _ZmlRK10ggSpectrumS1_/46520

with the following jump functions:
    callsite  main/48071 -> __comp_ctor /50391 : 
       param 0: UNKNOWN
         Alignment: 16, misalignment: 0

    callsite  __base_ctor /50390 -> __comp_ctor /49466 : 
       param 0: UNKNOWN
         Alignment: 16, misalignment: 0
->     param 1: ANCESTOR: 0, offset 192
         Unknown alignment
       param 2: ANCESTOR: 0, offset 704
         Unknown alignment
       param 3: ANCESTOR: 0, offset 448
         Unknown alignment
       param 4: UNKNOWN
         Alignment: 16, misalignment: 0
       param 5: UNKNOWN
         Alignment: 16, misalignment: 0
       param 6: UNKNOWN
         Alignment: 16, misalignment: 0
       param 7: UNKNOWN
         Alignment: 16, misalignment: 0

    callsite  __base_ctor /49465 -> operator*/46520 : 
       param 0: ANCESTOR: 0, offset 1088
         Unknown alignment
       param 1: PASS THROUGH: 1 op nop_expr
         Unknown alignment

from poking at things in the debugger, the offset that is marked down as
192 looks much more like 24 in reality.... and 24 times 8 is 192... oh
boy...

Reply via email to