This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/66666] ARM wrong copy constructor address on multiple inheritance
- From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 01 Jul 2015 10:18:44 +0000
- Subject: [Bug c++/66666] ARM wrong copy constructor address on multiple inheritance
- Auto-submitted: auto-generated
- References: <bug-66666-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66666
James Greenhalgh <jgreenhalgh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-07-01
Ever confirmed|0 |1
--- Comment #15 from James Greenhalgh <jgreenhalgh at gcc dot gnu.org> ---
(In reply to Antonio Poggiali from comment #14)
> >
> > Your toolchain is arm-none-linux-gnueabi , but you build with
> > -mfloat-abi=hard - do you have suitable hard-float libraries on the target?
> >
>
> I have only hard-float libraries and related system header files.
>
> > How was the toolchain configured
> > (arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++ -v)?
> >
>
> <Snip>
Thanks, I've reproduced the failure using the configuration above.
Looks like we can drop most of the command line arguments and still tickle the
segmentation fault
>
> > What userspace is running on the target?
>
> Sorry but I don't understand the question. Could you explain a little?
Debian/Ubuntu/Android etc. I've been able to reproduce it with a Ubuntu 12.04.4
userspace. But I haven't yet understood the issue.