From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alan Modra <amodra@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RS6000] PR88614, output_operand: invalid %z value
Date: Tue, 22 Jan 2019 00:35:00 -0000 [thread overview]
Message-ID: <20190122003455.GE14180@gate.crashing.org> (raw)
In-Reply-To: <20190122002957.GH29797@bubble.grove.modra.org>
On Tue, Jan 22, 2019 at 10:59:57AM +1030, Alan Modra wrote:
> > I think this would be nicer if you still used insn alternatives here.
> > What is needed for that?
>
> A new symbol constraint especially for __tls_get_addr? Actually two
> new constraints for ppc64, one for small model, the other for
> medium/large! No way.
You don't need new constraints I think; you can use the "enabled" attribute
for it. Not a stage4 thing I guess.
> > The patch is okay for trunk (if it survives on at least all three linux
> > targets). Thanks!
>
> Happily it did, even with -mno-tls-markers.
:-)
Segher
prev parent reply other threads:[~2019-01-22 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 22:59 Alan Modra
2019-01-18 22:02 ` Segher Boessenkool
2019-01-20 13:38 ` Alan Modra
2019-01-21 12:19 ` Alan Modra
2019-01-21 14:23 ` Segher Boessenkool
2019-01-22 0:30 ` Alan Modra
2019-01-22 0:35 ` Segher Boessenkool [this message]
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=20190122003455.GE14180@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.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).