Re: [Algorithms] Complexity of new hardware

[Richard M. <mi...@tr...>]

This is most definitely not an algorithm.

-- 
()()      Richard Mitton
( '.')
(")_(")       Beard Without Portfolio :: Treyarch

----- Original Message ----- 
From: "Jon Watte" <jw...@gm...>
To: "Game Development Algorithms" <gda...@li...>
Sent: Thursday, April 16, 2009 1:05 PM
Subject: [Algorithms] Complexity of new hardware


> Nicholas "Indy" Ray wrote:
>> On Thu, Apr 16, 2009 at 11:14 AM,
>> <chr...@pl...> wrote:
>>
>>> The fact that you have to rely on labelling assembly instructions
>>> and for-loops as "general components" to provide support for your
>>> initial statement shows how weak your statement was.
>>>
>>
>> Additionally with over 200 assembly instructions in x86, with more and
>> more special case assembly instructions being added, I wouldn't really
>>
>
> My favorite new x86 instruction:
> |
> vmadd231ps v0 {k1}, v5, [rbx+rcx*4] {4to16}
>
> Dealing with complexity is really becoming quite a chore, and our tools
> just aren't keeping up IMO.
> What good ways are you seeing of lifting game design and implementation
> up onto higher levels of abstraction? Is it just middleware, or will the
> middleware guys in turn need newer, better ways of doing things?
>
> Sincerely,
>
> jw
>
> |
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> GDAlgorithms-list mailing list
> GDA...@li...
> https://lists.sourceforge.net/lists/listinfo/gdalgorithms-list
> Archives:
> http://sourceforge.net/mailarchive/forum.php?forum_name=gdalgorithms-list
>