Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!pdn!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.sys.ibm.pc.programmer Subject: Re: No Aliasing Compile Option Keywords: Microsoft 6.0 C update woes Message-ID: <265D38E8.26DE@tct.uucp> Date: 25 May 90 13:53:44 GMT References: <1990May19.141401.4350@ux1.cso.uiuc.edu> <265861D7.3293@tct.uucp> <1990May23.234917.21858@uunet!unhd> Organization: ComDev/TCT, Sarasota, FL Lines: 28 According to al@unhd.unh.edu.UUCP (Anthony Lapadula): >In article <265861D7.3293@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes: >>Because aliasing is such a basic feature of the language, it is not >>fair to clue in the compiler: "Psst! This is one of those special >>programs that doesn't do aliasing. Unholster the benchmark gun." > >I suppose we should just give up helpful optimizations until >the compiler is smart enough to figure out when aliasing isn't present? Use whatever optimization you like for personal code. My only complaint is about the use of a C-subset compiler ("cc -Oa") to compile published benchmark programs that are misrepresented as C compiler benchmarks. >Hmmmm. How do you feel about "register"? Is that cheating? Nope. It's a part of standard C. >Just to add in my 2 cents, within the past year I've completed 2 >medium-sized programs (each ~10,000 lines) using MSC 5.1. >I was quite please (surprised? not quite) that the -Ox did *not* >break a single line of code. That's nice. It's also irrelevant. Just because other people restrict themselves to a C subset does not make Microsoft right for publishing C-subset benchmarks misrepresented as C benchmarks. -- Chip Salzenberg at ComDev/TCT ,