public inbox for
 help / color / mirror / Atom feed
From: Robin Dapp <>
To: Jeff Law <>,
Subject: Re: [RFC] postreload cse'ing vector constants
Date: Wed, 7 Sep 2022 17:33:43 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> Did you did any archeology into this code to see if there was any 
> history that might shed light on why it doesn't just using the costing 
> models?
This one was buried under some dust :)

commit 0254c56158b0533600ba9036258c11d377d46adf
Author: John Carr <>
Date:   Wed Jun 10 06:00:50 1998 +0000

    reload1.c (reload_cse_simplify_operands): Do not call gen_rtx_REG
for each alternative.

    Wed Jun 10 08:56:27 1998  John Carr  <>
            * reload1.c (reload_cse_simplify_operands): Do not call
            for each alternative.  Do not replace a CONST_INT with a REG
            the reg is cheaper.

    From-SVN: r20402

Back then we didn't have vectors I suppose but apart from that I don't
see a compelling reason not to unconditionally check costs from this.
It seems like we did even more unconditional replacing before it,
including CONST_INTs.


  reply	other threads:[~2022-09-07 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 14:40 Robin Dapp
2022-09-07 15:06 ` Jeff Law
2022-09-07 15:33   ` Robin Dapp [this message]
2022-09-07 15:49     ` Jeff Law
2022-09-08 13:04       ` Robin Dapp
2022-09-27 17:40         ` Robin Dapp
2022-09-27 19:39           ` H.J. Lu
2022-09-28 16:48             ` Robin Dapp
2022-11-03 12:38               ` Robin Dapp
2022-11-20 16:40                 ` Jeff Law

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).