This is the mail archive of the gcc-bugs@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]

c++/2269 additional information


hi all,

I've meanwhile obtained some additional information about the problem.
I've attached a file moc_qslider.ii that, when compiled, produces an
objectfile with one of the unresolved references mentioned in the bug
report, QSlider::valueChange(). I've also attached a file qslider.ii
that contains the implementation of QSlider::valueChange().

Looking at the exported symbols of both objects, moc_qslider.o contains
both a reference to QSlider::valueChange(), which is properly resolved
by the linker but also a reference to 'non-virtual thunk to
QSlider::valueChange()', which cannot be resolved. So why is this
reference emitted at all?

Also attached are outputs of 'objdump -x | c++filt' for both object
files as generated on my machine.

best regards
    Matthias

info.tgz


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