public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Paul Koning <paulkoning@comcast.net>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] genemit: Handle `const_double_zero' rtx
Date: Wed, 16 Dec 2020 20:43:01 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.21.2012162003550.2104409@eddie.linux-mips.org> (raw)
In-Reply-To: <3488E35A-C026-4E88-9429-CE6FD7B9363A@comcast.net>

On Wed, 16 Dec 2020, Paul Koning wrote:

> > NB the PDP-11 pieces affected here and tripping this assertion are I 
> > believe dead code, as these insns are only ever produced by splitters and 
> > do not appear to be referred by their names.  
> 
> Right; I gave them names for documentation purposes, after all insns are 
> allowed to have names whether or not the name is referenced or is a 
> required name for RTL generation.

 You can use `*foo' however to have it printed in dumps and be able to 
refer to it otherwise, while not producing callable `gen_foo' entrypoints.  
It is not a feature GCC has always had, but it's been around for a little 
while already.

  Maciej

      reply	other threads:[~2020-12-16 20:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 20:38 Maciej W. Rozycki
2020-12-15 23:20 ` Jeff Law
2020-12-16 11:35   ` Maciej W. Rozycki
2020-12-16 12:28     ` Richard Sandiford
2020-12-16 13:30       ` Maciej W. Rozycki
2021-01-05 23:51         ` Maciej W. Rozycki
2021-01-06 16:34           ` Richard Sandiford
2021-01-08  2:12             ` Maciej W. Rozycki
2020-12-16 19:19     ` Paul Koning
2020-12-16 20:43       ` Maciej W. Rozycki [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=alpine.LFD.2.21.2012162003550.2104409@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=paulkoning@comcast.net \
    /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).