From: Diego Novillo <dnovillo@redhat.com>
To: Mike Stump <mrs@apple.com>
Cc: Syd Polk <spolk@apple.com>, GCC List <gcc@gcc.gnu.org>
Subject: Re: Help restricting args of an intrinsic function
Date: Sat, 31 Jan 2004 18:24:00 -0000 [thread overview]
Message-ID: <1075562713.8251.266.camel@localhost.localdomain> (raw)
In-Reply-To: <72958959-53BB-11D8-9B07-003065BDF310@apple.com>
On Sat, 2004-01-31 at 02:02, Mike Stump wrote:
> > Syd's problem can only be addressed if you have some
> > minimal data flow information available.
>
> No. Enumeration constants don't require data flow. Intergral constant
> expressions don't require data flow.
>
Syd seems to be looking for anything that the compiler can prove is a
constant. Realizing that a pointer dereference is a compile time
constant *does* need dataflow info, however trivial.
> I don't think Syd needs anything
> as powerful as dataflow, just as powerful as fold.
>
Powerful != expensive. Why are you considering such a simple data flow
problem a non-starter?
> The problem is
> these are frontend concepts and they may need to be handled by frontend
> code.
>
No, they are not. Syd's test case with pointer dereferences is not
something you can solve with an FE hook.
Diego.
next prev parent reply other threads:[~2004-01-31 15:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 0:53 Syd Polk
2004-01-31 0:54 ` Ian Lance Taylor
2004-01-31 1:21 ` Syd Polk
2004-01-31 1:38 ` Ian Lance Taylor
2004-01-31 1:52 ` David Edelsohn
2004-01-31 2:00 ` Syd Polk
2004-01-31 2:03 ` David Edelsohn
2004-01-31 2:20 ` Syd Polk
2004-01-31 3:18 ` Syd Polk
2004-01-31 0:55 ` Diego Novillo
2004-01-31 1:07 ` Syd Polk
2004-01-31 1:42 ` Diego Novillo
2004-01-31 4:29 ` Mike Stump
2004-01-31 7:34 ` Diego Novillo
2004-01-31 7:45 ` Mike Stump
2004-01-31 18:24 ` Diego Novillo [this message]
2004-02-02 19:58 ` Mike Stump
2004-02-02 23:44 ` Syd Polk
2004-02-02 23:56 ` Richard Henderson
2004-02-03 0:29 ` Syd Polk
2004-02-03 0:39 ` Richard Henderson
2004-02-02 23:26 ` Joe Buck
2004-02-02 23:37 ` Mike Stump
2004-02-02 23:45 ` Joe Buck
2004-02-03 0:31 ` Mike Stump
2004-02-03 0:35 ` Daniel Jacobowitz
2004-02-03 1:16 ` Mike Stump
2004-02-03 1:56 ` Gabriel Dos Reis
2004-01-31 0:58 ` Ziemowit Laski
2004-01-31 1:38 ` Syd Polk
2004-01-31 8:12 ` Joseph S. Myers
2004-02-03 14:18 Etienne Lorrain
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=1075562713.8251.266.camel@localhost.localdomain \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mrs@apple.com \
--cc=spolk@apple.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).