From: Steve Ellcey <sellcey@imgtec.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: <jose.marchesi@oracle.com>, <gdb-patches@sourceware.org>
Subject: Re: Build failure with probe patch
Date: Thu, 19 Feb 2015 00:48:00 -0000 [thread overview]
Message-ID: <1424306916.27855.115.camel@ubuntu-sellcey> (raw)
In-Reply-To: <87wq3ercw0.fsf@redhat.com>
On Wed, 2015-02-18 at 18:57 -0500, Sergio Durigan Junior wrote:
> On Wednesday, February 18 2015, Steve Ellcey wrote:
>
> > Is anyone else seeing this error when building the top-of-tree gdb:
> >
> >
> > cc1: warnings being treated as errors
> > /scratch/sellcey/gdb-bug/src/gdb/gdb/dtrace-probe.c: In function 'dtrace_get_probes':
> > /scratch/sellcey/gdb-bug/src/gdb/gdb/dtrace-probe.c:624: warning: dereferencing type-punned pointer will break strict-aliasing rules
> > make[1]: *** [dtrace-probe.o] Error 1
>
> Thanks for your report.
>
> I don't see anything like this in any of our builders here:
>
> <http://gdb-build.sergiodj.net/waterfall>
>
> > I get this when building gdb on a CentOS 5 system with GCC 4.1.2 but I do not
> > see it when building on a Ubuntu 12.04 system with GCC 4.6.3. I am not sure
> > if this is due to the old GCC or if it is a legitimate error.
>
> According to:
>
> <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41874>
>
> This warning has been removed from GCC. And by looking at the code
> referenced by it, I don't see anything wrong there. So I'd say you can
> ignore this (and probably update your GCC).
>
I would like to avoid updating GCC if possible. I build on old systems
because some of our customers use old systems. I don't know if gdb has
a 'minimal GCC' that it can be compiled with like GCC and some other
projects have. I tried changing the definition of 'dof' to be '
bfd_byte *' instead of 'struct dtrace_dof_hdr *' and then casting it on
the call to dtrace_process_dof instead of the call to
bfd_malloc_and_get_section. That got rid of the type punning message
but I wound up seeing:
/scratch/gcc/nightly/src/binutils-gdb/gdb/dtrace-probe.c: In function
'dtrace_get_probes':
/scratch/gcc/nightly/src/binutils-gdb/gdb/dtrace-probe.c:64: warning:
'arg.expr' is used uninitialized in this function
make[1]: *** [dtrace-probe.o] Error 1
Which I do not understand at all. I will investigate some more and see
if there is a clean way to get this to compile with GCC 4.1.2.
Steve Ellcey
sellcey@imgtec.com
next prev parent reply other threads:[~2015-02-19 0:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 17:51 Steve Ellcey
2015-02-18 23:58 ` Sergio Durigan Junior
2015-02-19 0:48 ` Steve Ellcey [this message]
2015-02-19 4:39 ` Sergio Durigan Junior
2015-02-19 15:55 ` Jose E. Marchesi
2015-02-19 16:53 ` Pedro Alves
2015-02-19 17:32 ` Jose E. Marchesi
2015-02-19 17:48 ` Steve Ellcey
2015-02-19 20:41 ` Jose E. Marchesi
2015-02-19 21:18 ` Sergio Durigan Junior
2015-02-19 21:48 ` Steve Ellcey
2015-02-19 21:52 ` Sergio Durigan Junior
2015-02-19 21:59 ` Steve Ellcey
2015-02-19 18:30 ` Pedro Alves
2015-02-19 20:11 ` Jose E. Marchesi
2015-02-19 10:43 ` 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=1424306916.27855.115.camel@ubuntu-sellcey \
--to=sellcey@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=sergiodj@redhat.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