public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antonio.poggiali at datalogic dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66666] ARM wrong copy constructor address on multiple inheritance
Date: Tue, 30 Jun 2015 07:01:00 -0000	[thread overview]
Message-ID: <bug-66666-4-yBEIXWi1T3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66666-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Antonio Poggiali <antonio.poggiali at datalogic dot com> ---
(In reply to Mikael Pettersson from comment #10)
> (In reply to Antonio Poggiali from comment #9)
> > Sorry, this code:
> > 
> > https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/cgraphunit.
> > c?r1=221077&r2=221076&pathrev=221077
> 
> Yes, but I'm not convinced it's the real fix.

Unfortunately I can't use gcc 5 (I'm trying but it's not so easy) so, up to
now, this "patch" is the only way to get my system working.

Do you think this bug will be fixed in a new release (e.g. 4.9.4)?

Thank you!


  parent reply	other threads:[~2015-06-30  7:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 13:10 [Bug c++/66666] New: ARM compiled code segmentation fault " antonio.poggiali at datalogic dot com
2015-06-25 17:49 ` [Bug c++/66666] " ramana at gcc dot gnu.org
2015-06-26  7:04 ` antonio.poggiali at datalogic dot com
2015-06-26 11:23 ` antonio.poggiali at datalogic dot com
2015-06-26 11:24 ` antonio.poggiali at datalogic dot com
2015-06-27 12:42 ` [Bug c++/66666] ARM wrong copy constructor address " mikpelinux at gmail dot com
2015-06-28 12:40 ` mikpelinux at gmail dot com
2015-06-29 15:56 ` antonio.poggiali at datalogic dot com
2015-06-29 15:59 ` antonio.poggiali at datalogic dot com
2015-06-30  7:01 ` antonio.poggiali at datalogic dot com [this message]
2015-06-30 13:24 ` antonio.poggiali at datalogic dot com
2015-06-30 17:09 ` jgreenhalgh at gcc dot gnu.org
2015-07-01 10:18 ` jgreenhalgh at gcc dot gnu.org
2015-07-01 10:26 ` antonio.poggiali at datalogic dot com
2015-07-03 15:57 ` jgreenhalgh at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-66666-4-yBEIXWi1T3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).