From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: C++ conversion status update
Date: Tue, 15 Dec 2015 11:39:00 -0000 [thread overview]
Message-ID: <877fkglytf.fsf@oracle.com> (raw)
In-Reply-To: <566F13D4.9000900@redhat.com> (Pedro Alves's message of "Mon, 14 Dec 2015 19:09:08 +0000")
>> The question I have is which hosts (Architecture + OS combination) people
>> care about that still need C++ conversion work and thus should be on
>> that list?
>
> How about all linux and mingw hosts? assuming that xtensa can be
> converted.
x86-64 and x86 mingw built cleanly last I tried.
I don't know about _all_ Linux hosts, hence the RFH.
At least x86, x86_64, Aarch64, ARM, and PPC64 build cleanly. Or did, a
few weeks back.
In sparc-*-linux-gnu:
- Builds fine with GCC 6 (svn).
- Builds fine with GCC 4.9.1.
- Build fails with GCC 4.4.7:
g++ -g -O2 -I. -I../../gdb -I../../gdb/common -I../../gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../gdb/../include/opcode -I../../gdb/../opcodes/.. -I../../gdb/../readline/.. -I../../gdb/../zlib -I../bfd -I../../gdb/../bfd -I../../gdb/../include -I../libdecnumber -I../../gdb/../libdecnumber -I../../gdb/gnulib/import -Ibuild-gnulib/import -DTUI=1 -I/usr/include/python2.6 -I/usr/include/python2.6 -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wno-sign-compare -Wno-write-strings -Wno-narrowing -Wformat-nonliteral -Werror -c -o sparc64-tdep.o -MT sparc64-tdep.o -MMD -MP -MF .deps/sparc64-tdep.Tpo ../../gdb/sparc64-tdep.c
cc1plus: warnings being treated as errors
In file included from ../../gdb/target.h:74,
from ../../gdb/exec.h:23,
from ../../gdb/gdbcore.h:29,
from ../../gdb/sparc64-tdep.c:27:
../../gdb/btrace.h: In function ‘size_t VEC_btrace_insn_s_embedded_size(int)’:
../../gdb/btrace.h:84: error: invalid access to non-static data member ‘VEC_btrace_insn_s::vec’ of NULL object
../../gdb/btrace.h:84: error: (perhaps the ‘offsetof’ macro was used incorrectly)
../../gdb/btrace.h: In function ‘VEC_btrace_insn_s* VEC_btrace_insn_s_alloc(int)’:
../../gdb/btrace.h:84: error: invalid access to non-static data member ‘VEC_btrace_insn_s::vec’ of NULL object
../../gdb/btrace.h:84: error: (perhaps the ‘offsetof’ macro was used incorrectly)
../../gdb/btrace.h: In function ‘VEC_btrace_insn_s* VEC_btrace_insn_s_copy(VEC_btrace_insn_s*)’:
../../gdb/btrace.h:84: error: invalid access to non-static data member ‘VEC_btrace_insn_s::vec’ of NULL object
../../gdb/btrace.h:84: error: (perhaps the ‘offsetof’ macro was used incorrectly)
../../gdb/btrace.h: In function ‘VEC_btrace_insn_s* VEC_btrace_insn_s_merge(VEC_btrace_insn_s*, VEC_btrace_insn_s*)’:
../../gdb/btrace.h:84: error: invalid access to non-static data member ‘VEC_btrace_insn_s::vec’ of NULL object
../../gdb/btrace.h:84: error: (perhaps the ‘offsetof’ macro was used incorrectly)
../../gdb/btrace.h: In function ‘int VEC_btrace_insn_s_reserve(VEC_btrace_insn_s**, int, const char*, unsigned int)’:
../../gdb/btrace.h:84: error: invalid access to non-static data member ‘VEC_btrace_insn_s::vec’ of NULL object
../../gdb/btrace.h:84: error: (perhaps the ‘offsetof’ macro was used incorrectly)
At global scope:
cc1plus: error: unrecognized command line option "-Wno-narrowing"
make[2]: *** [sparc64-tdep.o] Error 1
make[2]: Leaving directory `/home/jemarch/couts2/binutils-gdb/build/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/home/jemarch/couts2/binutils-gdb/build'
make: *** [all] Error 2
next prev parent reply other threads:[~2015-12-15 11:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:07 Pedro Alves
2015-12-14 14:40 ` Yao Qi
2015-12-14 19:09 ` Pedro Alves
2015-12-15 11:39 ` Jose E. Marchesi [this message]
2015-12-15 20:03 ` Simon Marchi
2015-12-16 0:19 ` Pedro Alves
2015-12-16 0:21 ` Pedro Alves
2015-12-16 1:19 ` Simon Marchi
2015-12-16 20:11 ` Pedro Alves
2015-12-16 20:15 ` Pedro Alves
2015-12-16 20:30 ` Simon Marchi
2015-12-16 22:10 ` Pedro Alves
2015-12-16 22:59 ` Pedro Alves
2016-01-19 19:00 ` John Baldwin
2016-01-20 11:10 ` Pedro Alves
2016-01-20 23:33 ` John Baldwin
2016-01-21 11:38 ` Pedro Alves
2016-04-16 0:21 ` Pedro Alves
2016-04-18 16:51 ` Pedro Alves
2016-04-19 19:26 ` John Baldwin
2016-04-19 20:36 ` Pedro Alves
2016-04-19 21:40 ` John Baldwin
2016-04-19 22:20 ` Pedro Alves
2016-04-13 0:25 ` Pedro Alves
2016-04-13 11:07 ` Yao Qi
2016-04-13 14:13 ` Pedro Alves
2016-04-13 14:31 ` Sergio Durigan Junior
2016-04-13 12:41 ` Joel Brobecker
2016-04-13 14:04 ` Pedro Alves
2016-04-13 14:16 ` Joel Brobecker
2016-04-13 14:27 ` Luis Machado
2016-04-13 14:35 ` Marc Khouzam
2016-04-13 14:59 ` Joel Brobecker
2016-04-13 14:40 ` Pedro Alves
2016-04-18 17:29 ` Pedro Alves
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=877fkglytf.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
/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