public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <amylaar AT cygnus.co.uk>
To: rth AT cygnus.com (Richard Henderson)
Cc: amylaar AT cygnus.co.uk, gcc AT gcc.gnu.org
Subject: Re: what's required for builtin_memcpy to be inlined
Date: Mon, 13 Sep 1999 16:43:00 -0000	[thread overview]
Message-ID: <199909132341.AAA32438@phal.cygnus.co.uk> (raw)
In-Reply-To: <19990913120108.A24768@cygnus.com>

> And we do do that.  What he wants is to delay the expansion of
> __builtin_memcpy until after global constant propogation.

We do that only at expansion time now.  But we could also do it when
we have folded an argument to a builtin function that is coded as a
call_insn so far.

WARNING: multiple messages have this Message-ID
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: rth@cygnus.com (Richard Henderson)
Cc: amylaar@cygnus.co.uk, gcc@gcc.gnu.org
Subject: Re: what's required for builtin_memcpy to be inlined
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <199909132341.AAA32438@phal.cygnus.co.uk> (raw)
Message-ID: <19990930180200.kZZf_lliRZoHJZoAiwhD7a4GbTJR7PstFjMkj9Osd2M@z> (raw)
In-Reply-To: <19990913120108.A24768@cygnus.com>

> And we do do that.  What he wants is to delay the expansion of
> __builtin_memcpy until after global constant propogation.

We do that only at expansion time now.  But we could also do it when
we have folded an argument to a builtin function that is coded as a
call_insn so far.

  reply	other threads:[~1999-09-13 16:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-08 19:21 Artur Skawina
1999-09-08 19:35 ` Joe Buck
1999-09-09 14:39   ` Artur Skawina
1999-09-30 18:02     ` Artur Skawina
1999-09-30 18:02   ` Joe Buck
1999-09-09  1:47 ` Martin v. Loewis
1999-09-10  8:45   ` Jamie Lokier
1999-09-10 12:20     ` Richard Henderson
1999-09-10 15:33       ` Artur Skawina
1999-09-10 16:12         ` Richard Henderson
1999-09-13 10:31           ` Joern Rennecke
1999-09-13 12:01             ` Richard Henderson
1999-09-13 16:43               ` Joern Rennecke [this message]
1999-09-30 18:02                 ` Joern Rennecke
1999-09-30 18:02               ` Richard Henderson
1999-09-30 18:02             ` Joern Rennecke
1999-09-30 18:02           ` Richard Henderson
1999-09-30 18:02         ` Artur Skawina
1999-09-30 18:02       ` Richard Henderson
1999-09-10 13:47     ` Martin v. Loewis
1999-09-30 18:02       ` Martin v. Loewis
1999-09-30 18:02     ` Jamie Lokier
1999-09-30 18:02   ` Martin v. Loewis
1999-09-30 18:02 ` Artur Skawina

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=199909132341.AAA32438@phal.cygnus.co.uk \
    --to=gcc@gcc.gnu.org \
    /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).