From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2ac7208e3d69354f X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-18 09:26:14 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.tele.dk!small.news.tele.dk!194.25.134.62!newsfeed00.sul.t-online.de!newsmm01.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail From: Matthias Kretschmer Newsgroups: comp.lang.ada Subject: Re: Ada and vectorization Date: Tue, 18 Jun 2002 18:21:13 +0200 Organization: Private Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: news.t-online.com 1024417267 05 6874 nLhpbaISScYI3f 020618 16:21:07 X-Complaints-To: abuse@t-online.com X-Sender: 520099920815-0001@t-dialin.net User-Agent: KNode/0.7.1 Xref: archiver1.google.com comp.lang.ada:26260 Date: 2002-06-18T18:21:13+02:00 List-Id: Dale Stanbrough wrote: > In article , > Matthias Kretschmer wrote: > >> I think that today compilers - >> optimizers of compilers - are capable of finding places where to use >> vector units or what how ever so cool feature of you cpu, so I want them >> to decide and let me alone with the real important stuff. I do not want >> to know how many clock cycles A takes in unit B of cpu C. Think of what >> you have to know just to get something done, which other compilers do for >> their own without bothering the programmer. > > It would be nice if we let the compiler discover all of the possible > vectorisations possible. I've got no idea what the current state > of the art is in this respect, however I would imagine that it would > still be -cheaper- to build a simple compiler that took hints or > directions from the programmer about possible vectorisation. maybe cheaper, but let me cite Dijkstra: "Are you quite sure that all those bells and whistles, all those wonderful facilities of your so-called powerful programming languages belong to the solution set rather than to the problem set?" And this is the question we have to ask here I think, and I am quite sure, that vectorization hints belong to the problem set ... and looking at the compiler design people, they are doing a great job, what today a compiler does is not compareable to the stuff possible (or available) twenty years ago - there are definatively nice compiler implementations available today using all those nice feature of your cpu - so not all of course, but I don't think it is a solution to move all the logic in the language, so the programmer has to care about, it just let's the programmer to do all over the stuff again (somehow inventing the wheel everytime he writes down code again). The other advantage is, that old code can gain more performance without changing one line of code, just by using a newer version of a compiler or another compiler. Having all features architectures provide accessable through a language I think should be called assembler and has nothing to do with abstraction of the programming of the underlying hardware. Do we really want to implement every single feature cpu-designers provide in the language itself? Then we will have some very bloated, complex language which will raise the difficult level of programming in this language. And this is not the aim of "higher programming languages". They should make it easy, or we all could just use assembler. The reason why I personally use Ada is, that it is abstract, not that I have to care about the hardware and I think this is the way it should be. > > Does anyone have real info instead of my speculation? > > Dale -- Greetings Matthias Kretschmer