From: BALATON Zoltan <balaton@eik.bme.hu>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: "Dino Papararo" <skizzato73@msn.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
Programmingkid <programmingkidx@gmail.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"Howard Spoelstra" <hsp.cat7@gmail.com>,
"luigi burdo" <intermediadc@hotmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [RFC PATCH v2] target/ppc: Enable hardfloat for PPC
Date: Thu, 27 Feb 2020 12:54:58 +0100 (CET) [thread overview]
Message-ID: <alpine.BSF.2.22.395.2002271248380.21840@zero.eik.bme.hu> (raw)
In-Reply-To: <CAL1e-=iK1NEOr=ZRBm9XtJw7Mn_23w1ra74e3yDGbfKPVTA9zw@mail.gmail.com>
On Thu, 27 Feb 2020, Aleksandar Markovic wrote:
> I totally disagree with your using the term "hardfloat feature enabled" in
> this context, speaking about this particulat patch. This may be just
> wishful thinking. The right wording would be "hardfloat feature hacked", or
> "hardfloat feature fooled".
>
> The patch itself has the wrong, intentionally misleading and confusing
> title from the outset. It should be something like "target/ppc: Cheat
> hardfloat feature into beleiving that inexact flag is always set"
May I point out that the patch is RFC, meaning it's not meant to be merged
only to test it and provide feedback. Also the limitations were stated in
the commit message. There's no other easy way that I know to test if
hardfloat would work with PPC than forcing inexact bit to have it run with
hardfloat most of the time. Once it's tested what regression this would
cause (other than the expected inexact bit) then we can see if there are
any other problem with hardfloat and PPC or only this bit. Then we can
either change it to only not clear inexact bit like it's done on other
archs or do something else as even not clearing sticky inexact bit would
break the non-sticky counterpart PPC has. Breakage would be limited to the
non-sticky version and discussion was about if even that's unacceptable.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2020-02-27 11:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 17:10 [RFC PATCH v2] target/ppc: Enable hardfloat for PPC BALATON Zoltan
2020-02-18 17:38 ` BALATON Zoltan
2020-02-19 2:27 ` Programmingkid
2020-02-19 15:35 ` BALATON Zoltan
2020-02-19 18:28 ` Howard Spoelstra
2020-02-19 19:28 ` BALATON Zoltan
2020-02-20 5:43 ` Howard Spoelstra
2020-02-25 3:07 ` Programmingkid
2020-02-25 12:09 ` BALATON Zoltan
2020-02-26 10:46 ` Programmingkid
2020-02-26 11:28 ` BALATON Zoltan
2020-02-26 13:00 ` R: " luigi burdo
2020-02-26 13:08 ` Dino Papararo
2020-02-26 14:28 ` Alex Bennée
2020-02-26 15:50 ` Aleksandar Markovic
2020-02-26 17:04 ` G 3
2020-02-26 17:27 ` Aleksandar Markovic
2020-02-26 18:14 ` R: " Dino Papararo
2020-02-26 18:51 ` Aleksandar Markovic
2020-02-27 2:43 ` Programmingkid
2020-02-27 7:16 ` Aleksandar Markovic
2020-02-27 11:54 ` BALATON Zoltan [this message]
2020-02-26 18:09 ` R: " Alex Bennée
2020-03-02 0:13 ` Programmingkid
2020-03-02 4:28 ` Richard Henderson
2020-03-02 11:42 ` BALATON Zoltan
2020-03-02 16:55 ` Richard Henderson
2020-03-02 23:16 ` BALATON Zoltan
2020-03-03 0:11 ` Richard Henderson
[not found] ` <CAKyx-3Pt2qLPXWQjBwrHn-nxR-9e++TioGp4cKFC3adMN3rtiw@mail.gmail.com>
2020-03-04 18:43 ` Fwd: " G 3
2020-03-05 19:25 ` Richard Henderson
2020-03-02 17:10 ` Alex Bennée
2020-03-02 23:01 ` BALATON Zoltan
2020-02-26 22:51 ` R: " BALATON Zoltan
2020-02-20 20:13 ` Richard Henderson
2020-02-21 16:04 ` BALATON Zoltan
2020-02-21 16:11 ` Peter Maydell
2020-02-21 16:51 ` Aleksandar Markovic
2020-02-21 18:04 ` BALATON Zoltan
2020-02-21 18:26 ` Peter Maydell
2020-02-21 19:52 ` BALATON Zoltan
2020-02-26 12:28 ` Alex Bennée
2020-02-26 13:07 ` BALATON Zoltan
2020-04-10 13:50 ` 罗勇刚(Yonggang Luo)
2020-04-10 18:04 ` BALATON Zoltan
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=alpine.BSF.2.22.395.2002271248380.21840@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=aleksandar.m.mail@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=hsp.cat7@gmail.com \
--cc=intermediadc@hotmail.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=skizzato73@msn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.