Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [PATCH] avoid strict-aliasing warnings in gdbserver/linux-x86-low.c
Date: Wed, 27 Apr 2011 10:24:00 -0000	[thread overview]
Message-ID: <201104271124.09516.pedro@codesourcery.com> (raw)
In-Reply-To: <20110427014014.GB23480@codesourcery.com>

On Wednesday 27 April 2011 02:40:14, Nathan Froyd wrote:
> Tested on x86_64-unknown-linux-gnu.  OK to commit?

Okay, thanks!

> gdb/gdbserver/
>         * linux-x86-low.c (amd64_emit_const): Call memcpy instead of
>         casting pointers.
>         (amd64_emit_reg, amd64_emit_int_call_1, amd64_emit_void_call_2):
>         (i386_emit_const, i386_emit_reg, i386_emit_int_call_1):
>         (i386_emit_void_call_2): Likewise.

-- 
Pedro Alves


      reply	other threads:[~2011-04-27 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  1:40 Nathan Froyd
2011-04-27 10:24 ` Pedro Alves [this message]

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=201104271124.09516.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=froydnj@codesourcery.com \
    --cc=gdb-patches@sourceware.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