Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] [SPARC] callfuncs.exp: avoid spurious register differences in sparc64 targets.
Date: Thu, 19 Nov 2015 16:18:00 -0000	[thread overview]
Message-ID: <564DF643.6000407@redhat.com> (raw)
In-Reply-To: <87ziyam0yh.fsf@oracle.com>

On 11/19/2015 04:02 PM, Jose E. Marchesi wrote:
> 
> Hi all!  Ok to commit?
> 
> commit 50fa72dabc43ba7fabbd5d213013d78cd22e2342
> Author: Jose E. Marchesi <jose.marchesi@oracle.com>
> Date:   Thu Nov 19 10:55:06 2015 -0500
> 
>     callfuncs.exp: avoid spurious register differences in sparc64 targets.
>     
>     The Linux kernel disables the FPU upon returning to userland.  This
>     introduces spurious failures in the register preservation tests in
>     callfuncs.exp, since the pstate.PEF bit gets cleared after system calls.

> +	-re  "^pstate\[ \t\]+\[^\r\n\]+\r\n" {
> +	    if [istarget "sparc64-*-linux-gnu"] {
> +		# Filter out the pstate register, since in sparc64
> +		# targets the Linux kernel disables pstate.PEF when
> +		# returning from traps, giving spurious differences.

Isn't this a kernel bug?  It sounds like it's impossible to debug FPU
code if you e.g. step over FPU instructions?

> +	    } else {
> +		lappend all_registers_lines $expect_out(0,string)
> +	    }
> +	    exp_continue
> +	}

Thanks,
Pedro Alves


  reply	other threads:[~2015-11-19 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 15:55 Jose E. Marchesi
2015-11-19 16:18 ` Pedro Alves [this message]
2015-11-19 17:12   ` Jose E. Marchesi
2015-11-19 17:28     ` Pedro Alves
2015-11-20 10:29       ` Jose E. Marchesi

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=564DF643.6000407@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.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