On Fri, Aug 14, 2020 at 3:33 PM Matt Wette via Gcc wrote:
> Happy to see someone working this. Are you starting with one CC mode?
I'm also working on this (mostly at bug#92792), and so far am using
two modes: the general reg:CC mode for proper comparison insns, and
CCNZ for optimization in the
On Fri, Aug 14, 2020 at 4:24 PM Segher Boessenkool
wrote:
> On Fri, Aug 14, 2020 at 04:46:59PM +0530, Senthil Kumar Selvaraj via Gcc
> wrote:
> > (define_insn "*mov_insn_noclobber_flags"
> > [(set (match_operand:ALL1 0 "nonimmediate_operand" "=r,d ,q,r")
> > (match_operand:ALL1 1 "nox
On Sat, Aug 15, 2020 at 12:30 AM Segher Boessenkool
wrote:
> On Fri, Aug 14, 2020 at 05:47:02PM +, Pip Cet wrote:
> > On Fri, Aug 14, 2020 at 4:24 PM Segher Boessenkool
> > wrote:
> > > If you want to say some alternative does not clobber anything, just use
> > > the constraint "X" for that a
On Sun, Aug 16, 2020 at 12:50 AM Segher Boessenkool
wrote:
> On Sat, Aug 15, 2020 at 10:18:27AM +, Pip Cet wrote:
> > > > What I'm currently doing is this:
> > > >
> > > > (define_split
> > > > [(set (match_operand 0 "nonimmediate_operand")
> > > > (match_operand 1 "nox_general_operand")
On Mon, Aug 17, 2020 at 7:31 AM Senthil Kumar Selvaraj
wrote:
> > (define_split
> > [(parallel [(set (match_operand:ALL1 0 "nonimmediate_operand")
> > (match_operand:ALL1 1 "nox_general_operand"))
> > (clobber (reg:CC REG_CC))])]
> > "reload_completed && REG_P (operands[
On Tue, Aug 18, 2020 at 6:52 AM Senthil Kumar Selvaraj
wrote:
> > recognize such insns, but as it stands that define_insn would
> > recognize the incorrect insn:
> >
> > [(set (reg:QI 0) (const_int 0))
> > (clobber (scratch:CC))]
>
> get_cc_reg_clobber_rtx also looks at the insn itself (i.e. what
On Mon, Aug 24, 2020 at 6:18 PM Jeff Law wrote:
> > The post-reload splitter introduces the clobber. The wiki
> > suggests that approach if most insns clobber REG_CC, perhaps because of
> > the missed optimizations you describe below?
> If most patterns set/clobber the flags, then yes, it's slight
I may be missing an obvious workaround, but it seems we currently emit
a #line directive when including lines from machine description files
in C files, but never emit a second directive when switching back to
the generated C file. This makes stepping through the backend in gdb
somewhat painful, be
On Thu, Sep 3, 2020 at 8:19 PM Hans-Peter Nilsson wrote:
> On Thu, 27 Aug 2020, Pip Cet via Gcc wrote:
> > I may be missing an obvious workaround, but it seems we currently emit
> > a #line directive when including lines from machine description files
> > in C files, bu
"Andrew Pinski \(QUIC\) via Gcc" writes:
> Deprecating complex integer types in GCC seems like a good idea. There
> has been issues with division with them before and it was raised back
> them maybe we should deprecate their support.
> The previous discussion about deprecating them can be found
>
10 matches
Mail list logo