[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rep:Re: [f-cpu] new langage ?



Sorry,

But it seems than I never have receive the begining of this discussion.
Where can I get it ?
Perhaps the subject have been changed.

Bye,
Just an Illusion

Nicolas Boulay wrote:

>New language of a higher level is really needed to really have a code
>portability without the problem of performance.
>
>BUT it's really hard to devellop a all new language ( or look at "D" ).
>
>I personnaly like the way systemC work. It's only a "big" librairy for
>C++. We just have to design a librairy that work well with SIMD. 
>
>In c++, one librairy do such thing : STL. If we port STL (in asm) for
>the fpu we could accelerate all soon written programme and future one. 
>
>I think it's the better cost/benefit ratio.
>
>nicO
>
>-----Message d'origine-----
>De: djrom <pash.cracken@free.fr>
>A: f-cpu@seul.org
>Date: 19/04/02
>Objet: Re: [f-cpu] Winograd DCT on my seul.org account
>
>this is a very interesting paper. but what haven't you written the code
>in assembler ? the C code looks like assembler in any way, so ... :-)
>
>it cause the problem of gcc to (re)raise. optimisations for FC0 are very
>different from usual optimisations, even for RISC processors. I don't
>know the real structure of gcc, but I guess it'll be very difficult to
>put FC0 tricks without breaking the portability, no ? I even wonder if
>rewriting a new compiler won't be much easier than trying to add such
>things in gcc, if we want the compiler to be good. we don't want to see
>the F-Cpu ends like the PIV, used at less than 30%, right ? 
>moreover, we should perhaps think about another langage to be used on
>modern processors. C is very limited in his expressivity, so the
>operations like SIMD or "real" optimisations put a ton of work on the
>compiler's shoulders. it shouldn't just try to optimise, but it must
>even try to *understand* what the programmers meant. is there a langage
>really usable for modern RISC processors ? maybe we should try to return
>to lisp or ML, or something like that, no ? that's could also be a way
>to promote new langages: I don't want 2030's processors to be always
>coded in C ! :-) 
>
>if *we* don't promote new langages, we won't be able to count on Intel
>to do it ! :-)
>
>*************************************************************
>To unsubscribe, send an e-mail to majordomo@seul.org with
>unsubscribe f-cpu       in the body. http://f-cpu.seul.org/
>
> 
>______________________________________________________________________________
>ifrance.com, l'email gratuit le plus complet de l'Internet !
>vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
>http://www.ifrance.com/_reloc/email.emailif
>
>
>*************************************************************
>To unsubscribe, send an e-mail to majordomo@seul.org with
>unsubscribe f-cpu       in the body. http://f-cpu.seul.org/
>


*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/