From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: ian@wasabisystems.com, gcc@gcc.gnu.org
Subject: Re: Can we speed up the gcc_target structure?
Date: Mon, 19 Jan 2004 12:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0401191257460.14384@bellatrix.tat.physik.uni-tuebingen.de> (raw)
In-Reply-To: <10401191153.AA27414@vlsi1.ultra.nyu.edu>
On Mon, 19 Jan 2004, Richard Kenner wrote:
> My sense would be to revert these changes and eliminate the target stucture
> in favor of the simpler macro approach.
>
> Am I the only one who feels this way? If not, this may be an issue for the
> SC to address.
A better way would be to handle those target functions that can be const
with a hybrid approach like
#define TARGET_FUNCTION_FOO_CONST_VALUE false
static inline bool target_function_foo(...)
{
#ifdef TARGET_FUNCTION_FOO_CONST_VALUE
return TARGET_FUNCTION_FOO_CONST_VALUE;
#else
return vec->target_function_foo(...);
#endif
}
and for sanity
struct target_vector {
...
#ifndef TARGET_FUNCTION_FOO_CONST_VALUE
bool (*target_function_foo)(...);
#endif
...
};
or semantically similar approach. This way targets can decide, if they
want a modifiable target vector, or if they have a more complex
requirement.
Richard.
--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/
next prev parent reply other threads:[~2004-01-19 12:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 11:51 Richard Kenner
2004-01-19 12:01 ` Richard Guenther [this message]
2004-01-19 20:02 ` Richard Henderson
2004-01-19 14:16 ` Robert Dewar
2004-01-19 18:03 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2004-01-19 23:48 Richard Kenner
2004-01-19 23:42 Richard Kenner
2004-01-19 23:46 ` Zack Weinberg
2004-01-19 21:25 Richard Kenner
2004-01-19 23:36 ` Zack Weinberg
2004-01-19 19:05 Richard Kenner
2004-01-19 21:15 ` Zack Weinberg
2004-01-19 18:18 Richard Kenner
2004-01-19 18:26 ` Zack Weinberg
2004-01-18 22:18 Chris Lattner
2004-01-18 22:33 ` Jan Hubicka
2004-01-18 22:40 ` Chris Lattner
2004-01-18 22:48 ` Jan Hubicka
2004-01-18 22:50 ` Chris Lattner
2004-01-18 23:27 ` Jan Hubicka
2004-01-18 23:34 ` Jakub Jelinek
2004-01-19 1:36 ` Chris Lattner
2004-01-18 22:42 ` Joseph S. Myers
2004-01-18 22:44 ` Chris Lattner
2004-01-18 22:36 ` Richard Henderson
2004-01-18 22:42 ` Chris Lattner
2004-01-18 8:37 Ian Lance Taylor
2004-01-18 9:03 ` Zack Weinberg
2004-01-18 14:09 ` Ian Lance Taylor
2004-01-18 22:25 ` Zack Weinberg
2004-01-19 0:53 ` Ian Lance Taylor
2004-01-19 1:18 ` Geoff Keating
2004-01-18 11:30 ` Joseph S. Myers
2004-01-18 13:58 ` Kaveh R. Ghazi
2004-01-18 19:54 ` Ian Lance Taylor
2004-01-18 20:10 ` Richard Henderson
2004-01-18 20:17 ` Ian Lance Taylor
2004-01-18 21:14 ` Joseph S. Myers
2004-01-18 22:05 ` Richard Henderson
2004-01-18 22:22 ` Jan Hubicka
2004-01-18 22:37 ` Richard Henderson
2004-01-19 19:33 ` DJ Delorie
2004-01-19 20:41 ` Richard Henderson
2004-01-19 1:12 ` Geoff Keating
2004-01-19 13:51 ` Ian Lance Taylor
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=Pine.LNX.4.53.0401191257460.14384@bellatrix.tat.physik.uni-tuebingen.de \
--to=rguenth@tat.physik.uni-tuebingen.de \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).