From: Richard Biener <richard.guenther@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Alan Modra <amodra@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Add "cannot_copy" attribute, use it (PR67788, PR67789)
Date: Fri, 02 Oct 2015 08:31:00 -0000 [thread overview]
Message-ID: <CAFiYyc0p6EA9-2XzoVpoN+Ntx3NKWqg450q1aPVE0q9Qv++u4Q@mail.gmail.com> (raw)
In-Reply-To: <20151002011424.GA3657@gate.crashing.org>
On Fri, Oct 2, 2015 at 3:14 AM, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
> On Fri, Oct 02, 2015 at 10:24:07AM +0930, Alan Modra wrote:
>> On Thu, Oct 01, 2015 at 12:18:08PM -0500, Segher Boessenkool wrote:
>> > On Thu, Oct 01, 2015 at 12:14:44PM +0200, Richard Biener wrote:
>> > > So even if not "easy", can you try?
>> >
>> > I did, and after half a day had a big mess and lots of things failing,
>> > no idea where this was headed, and in the meantime bootstrap still fails
>> > (on affected targets).
>>
>> I had a look too, and while you can revise the load_toc_v4_PIC
>> patterns to use labels emitted the usual way (eg. as in
>> i386.c:ix86_init_large_pic_reg) they tend to wander away from the
>> insn.
>
> Yes, and only "bcl 20,31,$+4" avoids the link stack on recent CPUs
> (bcl 20,31,$+8, which we also use, doesn't).
>
>> I think that could be solved, but these labels which aren't
>> referred to by jump insns get converted to NOTE_INSN_DELETED_LABEL
>> somewhere, and that leads to further pain.
>
> Yes. You need to make the bcl a jump_insn to the label. And then
> there is yet more pain.
Sounds like supporting this with a special instruction in the assembler
would be easier then? ...
As for the compile-time hit, yes, calling the hook at all and having an
extra loop over all stmts in cfg_layout_can_duplicate_bb_p. There are
not many other uses of the hook, so I wonder if it is called everywhere
it has to be called.
Richard.
>
> Segher
next prev parent reply other threads:[~2015-10-02 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 6:09 Segher Boessenkool
2015-10-01 10:14 ` Richard Biener
2015-10-01 11:12 ` Bernd Schmidt
2015-10-01 17:18 ` Segher Boessenkool
2015-10-02 0:54 ` Alan Modra
2015-10-02 1:15 ` Segher Boessenkool
2015-10-02 8:31 ` Richard Biener [this message]
2015-10-01 14:05 ` David Edelsohn
2015-10-01 14:08 ` David Edelsohn
2015-10-01 17:39 ` Segher Boessenkool
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=CAFiYyc0p6EA9-2XzoVpoN+Ntx3NKWqg450q1aPVE0q9Qv++u4Q@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).