On Tue, Dec 03, 2019 at 12:57:24PM -0500, Michael Meissner wrote:
> No, the change for num_insns_constant_gpr could not go in until the support
> for
> PLI went in (patch V6 #1).
Well, I lost track. So your version 7 to 9 patches do *not* replace the
v6 patches? Or does "V" mean something else?
On Mon, Nov 25, 2019 at 06:49:49PM -0600, Segher Boessenkool wrote:
> On Mon, Nov 25, 2019 at 05:17:08PM -0500, Michael Meissner wrote:
> > On Fri, Nov 22, 2019 at 06:20:52PM -0600, Segher Boessenkool wrote:
> > > > (define_split
> > > >[(set (match_operand:SI 0 "gpc_reg_operand")
> > > >
On Mon, Nov 25, 2019 at 05:17:08PM -0500, Michael Meissner wrote:
> On Fri, Nov 22, 2019 at 06:20:52PM -0600, Segher Boessenkool wrote:
> > > (define_split
> > >[(set (match_operand:SI 0 "gpc_reg_operand")
> > > (match_operand:SI 1 "const_int_operand"))]
> > >"(unsigned HOST_WIDE_INT) (I
On Fri, Nov 22, 2019 at 06:20:52PM -0600, Segher Boessenkool wrote:
> On Thu, Nov 14, 2019 at 05:42:43PM -0500, Michael Meissner wrote:
> > -;; Split a load of a large constant into the appropriate two-insn
> > -;; sequence.
> > +;; Split a load of a large constant into the appropriate two-insn
>
On Thu, Nov 14, 2019 at 05:42:43PM -0500, Michael Meissner wrote:
> -;; Split a load of a large constant into the appropriate two-insn
> -;; sequence.
> +;; Split a load of a large constant into the appropriate two-insn sequence.
> On
> +;; systems that support PADDI (PLI), we can use PLI to load
This patch generates the PLI (PADDI) instruction to load up 32-bit SImode
constants on the future system. It adds an alternative to movsi, and prevents
the movsi load immediate from being split.
I have built compilers with this patch which bootstrapped fine, and there were
no regressions in the t
