Re: Unsafe Optimizations (formerly Compiler Design in C...)

grover@brahmand.Eng.Sun.COM (Vinod Grover)
Fri, 15 Jun 90 03:29:51 GMT

          From comp.compilers
Related articles
Unsafe Optimizations (formerly Compiler Design in C...) holub@violet.Berkeley.EDU (1990-06-12)
Re: Unsafe Optimizations (formerly Compiler Design in C...) moss@cs.umass.edu (1990-06-13)
Re: Unsafe Optimizations (formerly Compiler Design in C...) holub@violet.Berkeley.EDU (1990-06-14)
Re: Unsafe Optimizations (formerly Compiler Design in C...) marti@inf.ethz.ch (1990-06-14)
Re: Unsafe Optimizations (formerly Compiler Design in C...) larus@primost.cs.wisc.edu (1990-06-14)
Re: Unsafe Optimizations (formerly Compiler Design in C...) grover@brahmand.Eng.Sun.COM (1990-06-15)
Re: Unsafe Optimizations (formerly Compiler Design in C...) MERRIMAN@ccavax.camb.com (George Merriman -- CCA/NY) (1990-06-15)
Re: Unsafe Optimizations (formerly Compiler Design in C...) holub@violet.Berkeley.EDU (1990-06-15)
Re: Unsafe Optimizations (formerly Compiler Design in C...) pardo@june.cs.washington.edu (1990-06-15)
Re: Unsafe Optimizations (formerly Compiler Design in C...) barmar@Think.COM (1990-06-15)
Re: Unsafe Optimizations (formerly Compiler Design in C...) henry@zoo.toronto.edu (1990-06-20)
Re: Unsafe Optimizations (formerly Compiler Design in C...) dan@kfw.com (1990-06-20)
[7 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers
From: grover@brahmand.Eng.Sun.COM (Vinod Grover)
References: <1990Jun12.163959.2593@esegue.segue.boston.ma.us> <1990Jun13.143951.2129@esegue.segue.boston.ma.us> <1990Jun14.031936.5315@esegue.segue.boston.ma.us>
Date: Fri, 15 Jun 90 03:29:51 GMT
Organization: Sun Microsystems, Mt. View, Ca.
Keywords: code, optimize

In article <1990Jun14.031936.5315@esegue.segue.boston.ma.us> holub@violet.Berkeley.EDU () writes:
>does the compiler writer have any business deliberately restricting what the
>programmer can do simply because he or she doesn't think that the programmer
>has enough sense not to use a feature when it's not safe. I think not.


The question is whether the compiler writer has any business modifying the
semantics of a given language? I dont think so. No mater how "brain-dead" a
compiler writer thinks a particular feature is he should not circumvent it.
Think of the portability issues.


Vinod Grover
[Not to mention maintainability, see subsequent message. -John]
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.