public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Henri Cloetens <henri.cloetens@blueice.be>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Question on gcc RTL and scheduling step.
Date: Thu, 27 Feb 2020 09:23:00 -0000	[thread overview]
Message-ID: <20200226215937.GP22482@gate.crashing.org> (raw)
In-Reply-To: <41ecc0c2-0bda-f22f-549e-e7fc7b3a8c7f@blueice.be>

Hi!

On Wed, Feb 26, 2020 at 06:03:18PM +0100, Henri Cloetens wrote:
> ;; *      11--> b  0: i  44 
> {{%r31=%r31+0x18;%r0=[%r31+0x10];%r18=[%r31+0x8];clobber %r1;clobber 
> %r19;};pc=return;}:LDST**

This is a "slim" RTL dump, it leaves out quite a lot of important info,
like modes.  That info actually *is* there in the insn, usually, it just
isn't printed here.

> ***(insn:TI 44 27 28 2 (parallel [
>             (parallel [
>                     (set (reg/f:SI 31 %r31)
>                         (plus:SI (reg/f:SI 31 %r31)
>                             (const_int 24 
> [0x18])))
>                     (set (reg:DI 0 %r0)
>                         (mem/c:DI (plus:SI (reg/f:SI 
> 31 %r31)
>                                 (const_int 
> 16 [0x10])) [2  S8 A64]))
>                     (set (reg:DI 18 %r18)
>                         (mem/c:DI (plus:SI (reg/f:SI 
> 31 %r31)
>                                 (const_int 8 
> [0x8])) [2  S8 A64]))
>                     (clobber:SI (reg:DI 1 %r1))
>                     (clobber:SI (reg:DI 19 %r19))
>                 ])
>             (set (pc)
>                 (return))

Yeah, parallel of parallel, there is your problem.  You probably have a
parallel in a define_insn, but you already have an implicit one there?
A problem in your .md file, anyway.


Segher

      reply	other threads:[~2020-02-26 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 15:10 Henri Cloetens
2020-02-26 16:39 ` Segher Boessenkool
2020-02-26 17:02   ` Henri Cloetens
2020-02-26 22:00     ` Segher Boessenkool
2020-02-27  7:43       ` Henri Cloetens
2020-02-27  9:23         ` 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=20200226215937.GP22482@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=henri.cloetens@blueice.be \
    /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).