From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] nvidia scrolling performance
Date: Fri, 5 May 2006 12:22:23 -0500 [thread overview]
Message-ID: <9d075e1c7dfb3b8d3bc994ba5b3565c5@quanstro.net> (raw)
the abstract for glift contains this gem:
Glift enables GPU programmers to separate algorithms from data structure
definitions; thereby greatly simplifying algorithmic development [...]
has anyone considered a declaritive language for this sort of programming?
or are shaders too irregular for that sort of thing?
- erik
On Fri May 5 11:23:05 CDT 2006, plalonde@telus.net wrote:
>
> I'm really hoping that we can find a way to get our users off the C/C+
> + bandwagon (and that includes the high-level shading languages as
> well) and using something that can express the required computations
> more naturally. There are some promissing-looking functional
> approaches, but there's a huge barrier to adoption if it doesn't look
> like C.
>
> Paul
>
next reply other threads:[~2006-05-05 17:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 17:22 erik quanstrom [this message]
2006-05-05 17:32 ` Paul Lalonde
-- strict thread matches above, loose matches on Subject: below --
2006-05-05 18:08 erik quanstrom
2006-05-05 16:08 erik quanstrom
2006-05-05 16:42 ` David Leimbach
2006-05-05 15:46 erik quanstrom
2006-05-05 15:56 ` Paul Lalonde
2006-05-05 16:01 ` David Leimbach
2006-05-05 16:21 ` Paul Lalonde
2006-05-05 16:59 ` David Leimbach
2006-05-05 16:05 ` Wes
2006-05-05 17:07 ` Ronald G Minnich
2006-05-05 17:30 ` Paul Lalonde
2006-05-01 0:52 erik quanstrom
2006-05-01 1:00 ` Paul Lalonde
2006-05-01 0:30 erik quanstrom
2006-05-01 17:44 ` Russ Cox
2006-05-01 17:57 ` Artem Letko
2006-05-01 19:02 ` Russ Cox
2006-04-29 21:39 erik quanstrom
2006-04-30 4:00 ` jmk
2006-04-30 16:10 ` Russ Cox
2006-04-30 18:12 ` Steve Simon
2006-04-30 22:34 ` Ronald G Minnich
2006-05-01 6:52 ` Nigel Roles
2006-05-01 19:58 ` Ronald G Minnich
2006-05-01 20:10 ` David Leimbach
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=9d075e1c7dfb3b8d3bc994ba5b3565c5@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).