From: "Pedro Alves" <pedro_alves@portugalmail.pt>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Avoid gcc warning on sparc solaris 9
Date: Wed, 24 Oct 2007 13:28:00 -0000 [thread overview]
Message-ID: <4053daab0710240603k1efc5410r3c4eddb06979efd2@mail.gmail.com> (raw)
In-Reply-To: <200710231710.l9NHAUtT006558@d12av02.megacenter.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Ulrich Weigand wrote:
> Pedro Alves wrote:
>
> > Building HEAD on a native gdb on sparc solaris 9 with gcc 3.4.6 stops due to:
> >
> > ../../src/gdb/sol-thread.c: In function `sol_thread_fetch_registers':
> > ../../src/gdb/sol-thread.c:533: warning: dereferencing type-punned
> > pointer will break strict-aliasing rules
>
> We've seen this on other platforms with gcc 3.4 as well. I think
> the best fix would be replace the problematic construct
> supply_gregset (regcache, (const gdb_gregset_t *) &gregset);
> with
>
> gdb_gregset_t *gregset_p = &gregset;
>
> supply_gregset (regcache, (const gdb_gregset_t *) gregset_p);
>
> That seemed to fix the problems e.g. in i386-linux-nat.c (fetch_regs).
>
Indeed it does fix it here too. Much nicer. Thanks for the pointer.
Testsuite shows the same results as the previous version.
OK now?
--
Cheers,
Pedro Alves
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: solaris.diff --]
[-- Type: text/x-patch; name=solaris.diff, Size: 1244 bytes --]
2007-10-24 Pedro Alves <pedro_alves@portugalmail.pt>
* sol-thread.c (sol_thread_fetch_registers): Work around gcc 3.4
alias warning bug.
---
gdb/sol-thread.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
Index: src/gdb/sol-thread.c
===================================================================
--- src.orig/gdb/sol-thread.c 2007-10-23 17:07:07.604730000 +0100
+++ src/gdb/sol-thread.c 2007-10-24 13:35:37.380474000 +0100
@@ -484,6 +484,9 @@ sol_thread_fetch_registers (struct regca
td_err_e val;
prgregset_t gregset;
prfpregset_t fpregset;
+ gdb_gregset_t *gregset_p = &gregset;
+ gdb_fpregset_t *fpregset_p = &fpregset;
+
#if 0
int xregsize;
caddr_t xregset;
@@ -530,8 +533,8 @@ sol_thread_fetch_registers (struct regca
calling the td routines because the td routines call ps_lget*
which affect the values stored in the registers array. */
- supply_gregset (regcache, (const gdb_gregset_t *) &gregset);
- supply_fpregset (regcache, (const gdb_fpregset_t *) &fpregset);
+ supply_gregset (regcache, (const gdb_gregset_t *) gregset_p);
+ supply_fpregset (regcache, (const gdb_fpregset_t *) fpregset_p);
#if 0
/* FIXME: libthread_db doesn't seem to handle this right. */
next prev parent reply other threads:[~2007-10-24 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 16:46 Pedro Alves
2007-10-23 17:56 ` Ulrich Weigand
2007-10-24 13:28 ` Pedro Alves [this message]
2007-10-24 13:45 ` Ulrich Weigand
2007-10-24 13:48 ` Daniel Jacobowitz
2007-10-24 13:58 ` Pedro Alves
2007-10-24 14:56 ` Daniel Jacobowitz
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=4053daab0710240603k1efc5410r3c4eddb06979efd2@mail.gmail.com \
--to=pedro_alves@portugalmail.pt \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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