public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Rogerio Alves <rcardoso@linux.ibm.com>,
	"Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] power: Fix VSCR position on ucontext
Date: Thu, 10 Jan 2019 19:52:00 -0000	[thread overview]
Message-ID: <87k1jc5lzs.fsf@linux.ibm.com> (raw)
In-Reply-To: <ecf16bc6-c756-1147-4a72-03efbdd64ef4@linux.ibm.com>

Rogerio Alves <rcardoso@linux.ibm.com> writes:

> Subject: [PATCH v4] powerpc: Fix VSCR position in ucontext.
>
> This patch fix VSCR position on ucontext. VSCR was read in the wrong
> position on ucontext structure because it was ignoring the machine
> endianess.
>
> 2018-11-05  Rogerio A. Cardoso  <rcardoso@linux.ibm.com>
>
> 	* sysdeps/unix/sysv/linux/powerpc/sys/ucontext.h
>     (struct _libc_vscr, vscr_t): Added ifdef to fix read of VSCR.
> 	* sysdeps/powerpc/powerpc64/Makefile: Add tst-ucontext-ppc64-vscr.c
>     to test list.
> 	* sysdeps/powerpc/powerpc64/tst-ucontext-ppc64-vscr.c: New test file.


> /* This test is supported only on POWER 5 or higher.  */
> +#define PPC_CPU_SUPPORTED (PPC_FEATURE_POWER5 | PPC_FEATURE_POWER5_PLUS | \
> +                           PPC_FEATURE_ARCH_2_05 | PPC_FEATURE_ARCH_2_06 | \

The GNU Coding Standard requires to replace 8 spaces with a tab.
Fixed locally.   ;-)

> +		".machine \"power7\";\n"

s/power7/power5/
Fixed.

The patch looks good to me except for one thing: this is fixing a bug visible
to the user, so we also need a bug report for this.

Could you open the bug and send me the number?  I can incorporate it here
before pushing the patch.

Thanks!

-- 
Tulio Magno

  reply	other threads:[~2019-01-10 19:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 16:14 Rogerio Alves
2018-11-14 18:00 ` Florian Weimer
2018-11-16 13:18   ` Gabriel F. T. Gomes
2018-12-07 18:28     ` Rogerio Alves
2018-12-07 19:23       ` Gabriel F. T. Gomes
2018-12-10 17:18         ` Tulio Magno Quites Machado Filho
2018-12-10 18:12           ` Gabriel F. T. Gomes
2018-12-10 18:08         ` Gabriel F. T. Gomes
2018-12-10 18:25           ` Rogerio Alves
2018-12-10 21:20           ` Tulio Magno Quites Machado Filho
2018-12-19 19:30             ` Rogerio Alves
2019-01-10 19:52               ` Tulio Magno Quites Machado Filho [this message]
2019-01-11 12:01                 ` Szabolcs Nagy
2019-01-11 12:15                   ` Tulio Magno Quites Machado Filho
2019-01-11 19:52                 ` Tulio Magno Quites Machado Filho
2019-01-11 23:49                   ` Joseph Myers
2019-01-12  0:50                     ` Tulio Magno Quites Machado Filho

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=87k1jc5lzs.fsf@linux.ibm.com \
    --to=tuliom@ascii.art.br \
    --cc=fweimer@redhat.com \
    --cc=gabriel@inconstante.eti.br \
    --cc=libc-alpha@sourceware.org \
    --cc=rcardoso@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).