From: "H.J. Lu" <hjl@lucon.org>
To: GDB <gdb-patches@sources.redhat.com>
Cc: dan@codesourcery.com
Subject: PATCH: Work around another gcc 3.4 alias warning bug
Date: Mon, 16 Jul 2007 18:22:00 -0000 [thread overview]
Message-ID: <20070716180757.GA15193@lucon.org> (raw)
Hi,
Here is a patch to work around another gcc 3.4 alias warning bug
similar to:
http://sourceware.org/ml/gdb-patches/2007-06/msg00395.html
OK to install?
Thanks.
H.J.
----
2007-07-16 H.J. Lu <hongjiu.lu@intel.com>
* i386-linux-nat.c (fetch_regs): Work around gcc 3.4 alias
warning bug.
--- gdb/i386-linux-nat.c.const 2007-06-19 08:44:06.000000000 -0700
+++ gdb/i386-linux-nat.c 2007-07-16 11:02:35.000000000 -0700
@@ -246,6 +246,7 @@ static void
fetch_regs (struct regcache *regcache, int tid)
{
elf_gregset_t regs;
+ elf_gregset_t *regs_p = ®s;
if (ptrace (PTRACE_GETREGS, tid, 0, (int) ®s) < 0)
{
@@ -260,7 +261,7 @@ fetch_regs (struct regcache *regcache, i
perror_with_name (_("Couldn't get registers"));
}
- supply_gregset (regcache, (const elf_gregset_t *) ®s);
+ supply_gregset (regcache, (const elf_gregset_t *) regs_p);
}
/* Store all valid general-purpose registers in GDB's register array
next reply other threads:[~2007-07-16 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 18:22 H.J. Lu [this message]
2007-07-17 12:47 ` 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=20070716180757.GA15193@lucon.org \
--to=hjl@lucon.org \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sources.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