From: Peter Maydell <peter.maydell@linaro.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Taylor Simpson <tsimpson@quicinc.com>,
Riku Voipio <riku.voipio@iki.fi>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Hexagon: Swap SIGRGMAX-1 and SIGRTMIN+1
Date: Wed, 20 Nov 2019 11:00:32 +0000 [thread overview]
Message-ID: <CAFEAcA-mUps0qe9Ak6VjceZBAe=x9cQ3YPhhT9Qmg-c_XpqcDQ@mail.gmail.com> (raw)
In-Reply-To: <05b5c1b4-d1dd-7b82-cdf3-a1425edae499@vivier.eu>
On Wed, 20 Nov 2019 at 10:54, Laurent Vivier <laurent@vivier.eu> wrote:
> I understand your point, and I agree, but not allowing this will block
> the merge of the hexagon target, and I don't see any fix for the
> underlying problem coming soon.
>
> Other targets work without this change, and adding this change breaks
> some user space applications (like go), whereas adding this change for
> hexagon target only will improve the situation for it (with no
> regression, as it doesn't work at all for the moment)
I care more that we should fix things correctly and maintain the
consistency of how our architectures behave than that we are
able to quickly land a target for a fairly minor architecture,
to be honest. If we land hexagon with hacks and workarounds
then we're potentially stuck with that behaviour.
thanks
-- PMM
next prev parent reply other threads:[~2019-11-20 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 19:06 [PATCH] Hexagon: Swap SIGRGMAX-1 and SIGRTMIN+1 Taylor Simpson
2019-11-19 19:31 ` Peter Maydell
2019-11-20 5:23 ` Taylor Simpson
2019-11-20 8:09 ` Laurent Vivier
2019-11-20 10:45 ` Peter Maydell
2019-11-20 10:54 ` Laurent Vivier
2019-11-20 11:00 ` Peter Maydell [this message]
2019-11-20 12:54 ` Taylor Simpson
2019-11-21 11:29 ` Peter Maydell
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='CAFEAcA-mUps0qe9Ak6VjceZBAe=x9cQ3YPhhT9Qmg-c_XpqcDQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=tsimpson@quicinc.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 NNTP newsgroup(s).