Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nikola Prica <nikola.prica@rt-rk.com>
To: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>,
	Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org,
	"Ananthakrishna Sowda (asowda)" <asowda@cisco.com>,
	"Ivan Baev (ibaev)" <ibaev@cisco.com>,
	'Nemanja Popov' <nemanja.popov@rt-rk.com>,
	Djordje Todorovic <Djordje.Todorovic@rt-rk.com>,
	Ulrich.Weigand@de.ibm.com
Subject: Re: [PING][PATCH] Fix for prologue processing on PowerPC
Date: Thu, 11 Jan 2018 15:12:00 -0000	[thread overview]
Message-ID: <20038806-69e5-b7ce-479b-54185089145b@rt-rk.com> (raw)
In-Reply-To: <87r2qx4oit.fsf@linux.vnet.ibm.com>

Hi Pedro,

I understand it now. Thank you for explanation.

> I'm just not sure that the bitwise operations with
> lr_reg are safe considering it is an int (e.g., is lr_reg | 0x90010000
> well-defined?).
> 

Regarding that lr_reg is changed to valid value only when it is
previously set -1 and that it is changed like lr_reg = (op & 0x03e00000)
it means that it only takes bits between 21-26. I would say that it is
safe. I suppose that it is set to int for easier way of verifying its
validity.

Thanks,

Nikola Prica


  reply	other threads:[~2018-01-11 15:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 12:11 Nikola Prica
2017-10-05  2:01 ` Kevin Buettner
2017-10-26 10:02 ` [PING]Fix " Nikola Prica
2017-11-08 16:58   ` Kevin Buettner
2017-11-09 18:15     ` [PING][PATCH] Fix " Nikola Prica
2017-12-01 19:37       ` pedromfc
2017-12-19 15:57         ` Nikola Prica
2017-12-29 18:05           ` Pedro Franco de Carvalho
2018-01-09 11:22             ` Nikola Prica
2018-01-10 17:26               ` Pedro Franco de Carvalho
2018-01-11 15:12                 ` Nikola Prica [this message]
2018-01-19  7:49                   ` Nikola Prica
2018-01-19 19:01                     ` Pedro Franco de Carvalho
2018-01-19 19:08                     ` Pedro Franco de Carvalho
2018-01-27 14:32                       ` Nikola Prica
2018-01-31 18:04                         ` Pedro Franco de Carvalho
2018-01-31 18:28                           ` Ulrich Weigand
2018-02-01 13:09                             ` Nikola Prica
2018-01-02 10:29           ` Yao Qi

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=20038806-69e5-b7ce-479b-54185089145b@rt-rk.com \
    --to=nikola.prica@rt-rk.com \
    --cc=Djordje.Todorovic@rt-rk.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=asowda@cisco.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ibaev@cisco.com \
    --cc=kevinb@redhat.com \
    --cc=nemanja.popov@rt-rk.com \
    --cc=pedromfc@linux.vnet.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