public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Lucas A. M. Magalhaes" <lamm@linux.ibm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 2/3] powerpc64le: Check HWCAP bits against compiler build flags
Date: Tue, 18 May 2021 14:26:44 -0300	[thread overview]
Message-ID: <87tun0j6ln.fsf@linux.ibm.com> (raw)
In-Reply-To: <874kf05672.fsf@oldenburg.str.redhat.com>

Florian Weimer <fweimer@redhat.com> writes:

> What about this instead?
>
>   /* This check is not actually reached when building for POWER10 and
>      running on POWER9 because there are faulting PCREL instructions
>      before this point.  */

LGTM

-- 
Tulio Magno

  reply	other threads:[~2021-05-18 17:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 12:30 [PATCH 0/3] Checking HWCAP bits against compiler flags Florian Weimer
2021-05-06 12:30 ` [PATCH 1/3] elf: Add hook for checking HWCAP bits after auxiliary vector parsing Florian Weimer
2021-05-12  7:43   ` Stefan Liebler
2021-05-06 12:30 ` [PATCH 2/3] powerpc64le: Check HWCAP bits against compiler build flags Florian Weimer
2021-05-11 21:12   ` Lucas A. M. Magalhaes
2021-05-12  8:27     ` Florian Weimer
2021-05-12 14:50       ` Lucas A. M. Magalhaes
2021-05-12 14:52       ` Tulio Magno Quites Machado Filho
2021-05-12 17:27         ` Florian Weimer
2021-05-12 19:24           ` Tulio Magno Quites Machado Filho
2021-05-18 16:59         ` Florian Weimer
2021-05-18 17:26           ` Tulio Magno Quites Machado Filho [this message]
2021-05-18 17:41             ` Florian Weimer
2021-05-06 12:30 ` [PATCH 3/3] s390x: Check HWCAP bits against compiler flags Florian Weimer
2021-05-12  7:43   ` Stefan Liebler

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