From: Joern Rennecke <amylaar@cygnus.co.uk>
To: rth@cygnus.com (Richard Henderson)
Cc: skawina@geocities.com, jamie.lokier@cern.ch,
martin@mira.isdn.cs.tu-berlin.de, gcc@gcc.gnu.org
Subject: Re: what's required for builtin_memcpy to be inlined
Date: Mon, 13 Sep 1999 10:31:00 -0000 [thread overview]
Message-ID: <199909131728.SAA31642@phal.cygnus.co.uk> (raw)
In-Reply-To: <19990910161127.B14062@cygnus.com>
> On Fri, Sep 10, 1999 at 10:51:25PM +0200, Artur Skawina wrote:
> > [I'm not complaing that __builtin_constant_p got smarter -- that's
> > a very good thing in itself, and I hope it gets even smarter. It's
> > just that a __builtin_constant_p that is smarter then a builtin
> > string routine makes the latter much less useful...]
>
> Perhaps in the moderately near future we'll be able to do
> something about this. Nothing near-term though.
Well, wouldn't this depend on code contributions?
I think it should be faily straightforward to fold builtin function calls
when their arguments are constant.
WARNING: multiple messages have this Message-ID
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: rth@cygnus.com (Richard Henderson)
Cc: skawina@geocities.com, jamie.lokier@cern.ch,
martin@mira.isdn.cs.tu-berlin.de, 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: <199909131728.SAA31642@phal.cygnus.co.uk> (raw)
Message-ID: <19990930180200.EY1Ofq9yMDh87iw338OftZYQu2c8jaOty7t5G2joB8Q@z> (raw)
In-Reply-To: <19990910161127.B14062@cygnus.com>
> On Fri, Sep 10, 1999 at 10:51:25PM +0200, Artur Skawina wrote:
> > [I'm not complaing that __builtin_constant_p got smarter -- that's
> > a very good thing in itself, and I hope it gets even smarter. It's
> > just that a __builtin_constant_p that is smarter then a builtin
> > string routine makes the latter much less useful...]
>
> Perhaps in the moderately near future we'll be able to do
> something about this. Nothing near-term though.
Well, wouldn't this depend on code contributions?
I think it should be faily straightforward to fold builtin function calls
when their arguments are constant.
next prev parent reply other threads:[~1999-09-13 10:31 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 [this message]
1999-09-13 12:01 ` Richard Henderson
1999-09-13 16:43 ` Joern Rennecke
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=199909131728.SAA31642@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=jamie.lokier@cern.ch \
--cc=martin@mira.isdn.cs.tu-berlin.de \
--cc=rth@cygnus.com \
--cc=skawina@geocities.com \
/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).