Slashdot Mirror


Open Watcom 1.0 Released

JoshRendlesham writes "The Open Watcom C/C++ and FORTRAN 1.0 compilers have been officially released. The source, and binaries for Win32 and OS/2 systems, are available. This release also means that outside developers can join and contribute to the project." Or if you prefer, gcc is up to 3.2.2.

287 comments

  1. Rise of the Triads by Anonymous Coward · · Score: 3, Interesting

    Does this mean that I can finally use the ROTT-source for something else than just looking at? :-)

    1. Re:Rise of the Triads by Swootech · · Score: 2, Interesting

      Make a OS/2 port of ROTT then ;)

    2. Re:Rise of the Triads by Anonymous Coward · · Score: 0

      I do understand that you were trying to be funny, but still, one should note that the code had been ported to compile with gcc a day after the source code was released. http://www.icculus.org/rott/ has the code.

    3. Re:Rise of the Triads by Anonymous Coward · · Score: 0

      what. like playing it?
      http://www.icculus.org/rott/ was available literally days after the source went up, with a playable port.

      ashridah

    4. Re:Rise of the Triads by stg · · Score: 1

      Maybe, but why would you want to? :-)

  2. Open C-64 0.9 is now available. by thammoud · · Score: 1

    Enjoy all the powerfull features of the 8 bit C64 for free!!!

    1. Re:Open C-64 0.9 is now available. by Anonymous Coward · · Score: 1, Interesting

      Check out CC65. It is a pretty good freestanding implentation of ANSI C89 on the 6502 (C-64, Apple //, Atari 800, Nintendo, etc). Projects such as uIP and uVNC have been built with it.

  3. DOS days by Graspee_Leemoor · · Score: 4, Interesting

    Back in the days of DOS, if you were a developer, the Watcom C compiler was *the* thing to pirate.

    graspee

    1. Re:DOS days by frankjr · · Score: 1

      I bought the thing when I was 13. It took every bit of spare change I could manage to get a hold of...

    2. Re:DOS days by ctr2sprt · · Score: 5, Informative
      Wasn't it the first mainstream compiler to include a complete DOS extender and feature full 32-bit support? I remember wanting it so badly in the DOS days, but I was a broke student and could barely afford the modem I used to download porn. I had to make do with Borland C++ (which was great, but lacked 32-bit support unless you felt like writing a lot of assembler).

      Anyway, I'm excited by this because, well, competition is almost always a good thing. Hopefully gcc and Watcom can feed off each other and both products will improve. And perhaps more importantly for the build-everything users, another open source compiler might start moving people (like the developers of autoconf) to better support non-gcc compilers. This way, users who prefer Watcom's (or Intel's, or...) compiler can use it without as much tweaking.

    3. Re:DOS days by Anonymous Coward · · Score: 0

      Of course - DOS didn't come with a compiler. Linux does.

    4. Re:DOS days by Graspee_Leemoor · · Score: 5, Informative

      The version of gcc for dos: DJGPP had a DOS extender and 32-bit support but it was slower than Watcom by a large amount.

      graspee

    5. Re:DOS days by Anonymous Coward · · Score: 3, Funny

      Me too. I had to rob several convenience stores to save enough too buy the software, because I didn't want to pirate it.

    6. Re:DOS days by ma++i+ude · · Score: 3, Interesting
      First of all, for the uninitiated, if your program shipped with dos4gw.exe (as most games did), it was compiled in Watcom. Such was the performance difference that nobody really bothered with any other compiler, especially with games.

      Back in the days of DOS, if you were a developer, the Watcom C compiler was *the* thing to pirate.

      I remeber using a stripped-down copy which was missing a good part of the standard C++ libraries and still doing most of my development on it. Having gotten used to such luxuries as the IDE Borland C++ (and Turbo Pascal) shipped with, it took a while to get used to but produced superb code.

      --
      You can't shut us down! The Internet is about the free exchange and sale of other people's ideas!
    7. Re:DOS days by TheJesusCandle · · Score: 1, Redundant

      gcc could do with some competition, yes its stable, no it is not at the leading edge of performance any more, processor optimization is at least a generation behind what's commonly available and ignores some architectures completely.

      I'm looking forward to someone benchmarking gcc vs watcom to see how they do.

    8. Re:DOS days by mrfrostee · · Score: 1

      Wasn't it the first mainstream compiler to include a complete DOS extender and feature full 32-bit support?

      No, I think that was Zortech

    9. Re:DOS days by bawb · · Score: 2, Interesting

      it took a while to get used to but produced superb code

      Personally, I found it to be a disappointment and all my side-by-side comparisons with Borland's Turbo C++ usually fell short. Especially if I was unrolling a lot of loops. IIRC, snooping the output revealed that it ignored them and no amount of tweaking the compiler would correct it.

      There's no arguing that Watcom made it pretty easy to access more memory, but if you already had a code base set up to handle that there didn't seem to be much of a point.

    10. Re:DOS days by Exiler · · Score: 2, Funny

      No it doesn't. Your favorite distro might, but last I checked the Linux kernel does not come with a compiler, maybe you're talking about Emacs?

      --
      Banaaaana!
    11. Re:DOS days by moonbender · · Score: 1

      What exactly did dos4gw.exe do, incidently? I always used to wonder.

      --
      Switch back to Slashdot's D1 system.
    12. Re:DOS days by ma++i+ude · · Score: 5, Informative
      What exactly did dos4gw.exe do, incidently? I always used to wonder.
      It allowed the programmer to use all of the available memory. Remember when you had problems getting programs running because there was not enough conventional memory (ie. the first 640KB)? Well, dos/4gw made is easy to write programs free of these memory limitations. More information at http://www.tenberry.com/dos4g/
      --
      You can't shut us down! The Internet is about the free exchange and sale of other people's ideas!
    13. Re:DOS days by MadocGwyn · · Score: 1

      First of all, for the uninitiated, if your program shipped with dos4gw.exe (as most games did), it was compiled in Watcom

      Not true, back in my school daze, we used Turing a teaching language, and the newer version (at the time) Object Oriented Turing(OOT) used the same dos extender, it simply allowed dos level programs to access memeory above the 640k barrior, a godsend at the time

      --
      Jesus saves, everyone else takes full damage from the fireball.
    14. Re:DOS days by ma++i+ude · · Score: 1
      Not true, back in my school daze, we used Turing a teaching language, and the newer version (at the time) Object Oriented Turing(OOT) used the same dos extender, it simply allowed dos level programs to access memeory above the 640k barrior, a godsend at the time

      Are you sure? I always thought the 'W' in dos4gw.exe stands for Watcom.

      Anyway, the comparison table at http://www.tenberry.com/dos4g/watcom/4gwtable.htm lists Watcom C++ and Fortran as the only supported compilers. I thought there was a dos/4g available for some other products, but dos4gw.exe was exclusive to Watcom.

      Can someone verify this?

      --
      You can't shut us down! The Internet is about the free exchange and sale of other people's ideas!
    15. Re:DOS days by Ninja+Programmer · · Score: 2, Informative

      More specifically, it "EXTENDED DOS" to the 32 bit flat address model. The problem was that the entire DOS API was 16 bit, and assumed that everything happened in the first 640K. So if you wanted to use the DOS services with your data that was not in the first 640K, you needed a translation layer -- this is what the DOS Extender (typically via an API called "DPMI" -- DOS Protected Mode Interface) provides.

      Some of the better DOS Extenders had a built-in virtual memory mechanism as well. Actually it turned out that DOS4GW was kind of weak in comparison to the other extenders like "CauseWay" which Open Watcom is supposed to be using now.

    16. Re:DOS days by be-fan · · Score: 1

      If you'd take a look at the Coyote Gulch GCC vs ICC benchmarks, you'd realize, that for P6 class processors (P3 and Athlon) GCC is right up there with ICC. It has some issues with P7 processors (Pentium 4) but it's only a matter of time before those are fixed. Now I don't know how well it works for non-x86 architectures (which Watcom and ICC don't support) but it's x86 code is damn good.

      --
      A deep unwavering belief is a sure sign you're missing something...
    17. Re:DOS days by Mike+Monett · · Score: 3, Interesting

      More specifically, it "EXTENDED DOS" to the 32 bit flat address model. The problem was that the entire DOS API was 16 bit, and assumed that everything happened in the first 640K. So if you wanted to use the DOS services with your data that was not in the first 640K, you needed a translation layer -- this is what the DOS Extender (typically via an API called "DPMI" -- DOS Protected Mode Interface) provides.

      You can run 32 bit code in dos without the restrictions and performance penalty of DPMI. It's called Flat Real mode, and has been around since 1988. Himem and Smartdrv use it to access extended memory.

      But you don't have to go through Himem to access memory above 1 meg. You can do it yourself and eliminate the time wasted.

      The problem is debugging your code to ensure data is transferred correctly. DOS debuggers cannot recognize 32-bit addresses, so you cannot verify data is stored correctly or that you are pointing to the correct area in memory.

      Here's the solution

      http://www3.sympatico.ca/add.automation/flat/frm.h tm

      Best Regards,

      Mike Monett

    18. Re:DOS days by Anonymous Coward · · Score: 0

      Too bad there's no interprocedural or whole-program analysis and probably won't be in the near future.

    19. Re:DOS days by egoots · · Score: 1

      I belive PharLap was one of the first pioneers of dos extenders (companies like QEMM used them). Their 386-Dos extender was first released in 1986. I believe one of the original extended memory protocols was called VCPI. The DPMI protocol was done later on, with a number of companies, such as Rational, and Microsoft participating in its development and standardization.

      Interestingly enough, Microsoft supported DPMI in Win95 (Dos box/Dos mode), but Microsoft never ever implemented the full DPMI v1.0 spec. They only ever implemented DPMI 0.9. Some believed, that in doing so they helped encourage the transition of applications to be rewritten natively for Windows

    20. Re:DOS days by Anonymous Coward · · Score: 0

      You had digital porn in the DOS days? On the 16-color CGA screen? Those were not 16 flesh tints you know (or did you mod your CGA card...).

      Or was it all ASCII art?

    21. Re:DOS days by Reziac · · Score: 2, Funny

      Not to mention that DJGPP is responsible for the worldwide shortage of sacrificial chickens and goats!! Installing it has been described as a black art, and getting good performance from the resulting binaries.. lordy. Talk about bad juju.

      (And will someone PLEASE fix the stack overflow/memory leak in CWSDPMI?? It's been there since the Go32v2 days!!)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    22. Re:DOS days by Avakado · · Score: 1

      Hopefully gcc and Watcom can feed off each other and both products will improve.

      As far as I know, the copyright for the code needs to be handed over to FSF it it is to be used in the GNU compiler collection. I don't think that's very likely to happen. (This has nothing to do with license compatibilities, but rather FSF's policy)

      --
      The world will end in 5 minutes. Please log out.
    23. Re:DOS days by dmanny · · Score: 1
      Don't know who mod'ed you redundant on this. You expressed your opinion, other posters countered. People who post counterpoints advance discussion -- people who just down mod what they dislike are not as helpful.

      Anyway, I am meta-modding one "redundant" as "unfair".

      --
      All my previous sigs now look like this one, I wish they were permanetly recorded when used. :-(
  4. Good old days by Anonymous Coward · · Score: 1, Interesting

    I remember those old days that doom was written and compiled using Watcom C compiler. Just wondering what they(watcom) are up to now.

    1. Re:Good old days by jfpoole · · Score: 1

      Just wondering what they(watcom) are up to now.

      Watcom got bought out by PowerSoft, who in turn got bought out by Sybase. Sybase then spun off what used to be Watcom as iAnywhere Solutions. There's a bit of corporate history available here.

      As for what iAnywhere is currently developing, there's a list of products available here. iAnywhere focuses on databases these days; they no longer develop compilers.

  5. cool ! that's great news by jacquesm · · Score: 2, Interesting

    I used the watcom tools extensively on QNX and they were of excellent quality, this is really good news !

    Hopefully this sets a trend.

    1. Re:cool ! that's great news by Animats · · Score: 4, Interesting
      QNX uses the GNU/GCC toolchain now, and ship their premium product with the Dinkumware C++ library.

      Incidentally, if someone can tell me how to prevent loader crashes in "ld" under QNX when there's an undefined symbol in a trivial program that includes "", I'd appreciate it. Nobody in the QNX newsgroups seems to know.

    2. Re:cool ! that's great news by Anonymous Coward · · Score: 0

      "That's because nobody programs for QNX except you. Why don't you program for a real OS [microsoft.com]?"

      I bow at your trolling might, master!!

    3. Re:cool ! that's great news by Q+Who · · Score: 1, Flamebait

      Yeah! I have such problems too -- just today I wrote this trivial hello-world program and it just won't print anything!

      #include ""

      int main()
      {
      std::cout << "" << std::endl;
      }
    4. Re:cool ! that's great news by Animats · · Score: 1
      Meant includes "vector", but put it in corner brackets, so it looked like HTML.


      Why QNX? Because it's a real-time application.

    5. Re:cool ! that's great news by vandy1 · · Score: 1
      Methinks you may want to
      #include <iostream>
      ... You won't find
      #include ""
      doing anything much, except perhaps a compiler error about no such file :)
  6. Just don't... by gearheadsmp · · Score: 2, Informative

    use gcc-3.2.1-r6. It really fscks up Gentoo installations, and I don't think it's all that healthy for other distros either.

    1. Re:Just don't... by Anonymous Coward · · Score: 0

      The new GCC has incompatible C++ ABI changes. That's probably what's causing your problems.

    2. Re:Just don't... by Anonymous Coward · · Score: 0

      -r6 is Gentoo's way of tracking revisions of ebuild scripts. It has nothing to do with the actual GCC revisions, fact there is no "GCC 3.2.1-r6". So gentoo installations are all it'll fuck up, and all it can fuck up. If you're going to pretend to be a Gentoo monkey, at least get the terminology straight.

    3. Re:Just don't... by commanderfoxtrot · · Score: 2, Informative

      No, 3.2.1-r6 does not ruin Gentoo machines. There were a couple of initial problems due to a lack documentation on *how* to upgrade GCC. Take a look at the "Gentoo Weekly Newsletter" of a few weeks back.

      I have run 3.2.1r6 on my Gentoo machines since it came out with no problems whatsoever.

      BTW, anyone know when some more Duron/Morgan specific optimisations will appear? I'm using cpu=athlon-xp at the moment...

      --
      http://blog.grcm.net/
    4. Re:Just don't... by Evil-G · · Score: 1

      Really? I've used it for my gentoo installation, and not had a problem at all. hmm....

    5. Re:Just don't... by gearheadsmp · · Score: 1

      In my case, I tried upgrading to 3.2.1-r6 after doing an install and setting up xfce. After upgrading my packages to the latest and installing r6, I rebooted. *poof* my system ground to a halt after boot the kernel, and acted as if the hard drive hadn't been mounted. None of the daemons would start.

    6. Re:Just don't... by Anonymous Coward · · Score: 0

      using gentoo with 3.2.1-r6 without any problem on serval computers and notebooks.

      # qpkg -I -v -nc gcc;cat /etc/gentoo-release;gcc --version
      sys-devel/gcc-3.2.1-r6
      sys-devel/gcc-c onfig-1.2.7
      Gentoo Base System version 1.4.2.8
      gcc (GCC) 3.2.1 20021207 (Gentoo Linux 3.2.1-20021207)
      Copyright (C) 2002 Free Software Foundation, Inc.
      This is free software; see the source for copying conditions. There is NO
      warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

    7. Re:Just don't... by be-fan · · Score: 1

      There's no such thing as gcc 3.2.1-r6. The 'r6' is a Gentoo ebuild revision. GCC 3.2.1 works just fine. I'm on Gentoo, and I was using 3.2.1-r7 without any problems.

      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:Just don't... by Anonymous Coward · · Score: 0

      Don't worry. The problem isn't Gentoo, GCC, or GCC's ABI change- everything is fscked up because you are using Linux. Get used to it, it will probably happen about once a month. You get what you pay for.

  7. Re:Stop duplication of effort by jacquesm · · Score: 4, Interesting
    gcc could do with some competition, yes its stable, no it is not at the leading edge of performance any more, processor optimization is at least a generation behind what's commonly available and ignores some architectures completely.


    I'm looking forward to someone benchmarking gcc vs watcom to see how they do.

  8. Watcom was great. How about today? by CresentCityRon · · Score: 5, Interesting

    In the late 80s (?) Watcom products were really great. They were beating on everything for the Intel platform.

    I received the email yesterday about Watcom's "release" to open source. In that email it says that Sybase felt there was no commercial value in the product anymore so they released it. My question is "Has Sybase been keeping this thing up? Is it useful today?" Or is this a scam to try to give life to a dying patient? I mean perhaps people working on this might be better off working on gcc or something.

    Thanks!

  9. Superb! by occamboy · · Score: 2, Funny

    Another version of FORTRAN! Yeah! Now if I can just find a card punch machine and reader on eBay, I'll have hutled into the 1970s!

    1. Re:Superb! by grub · · Score: 5, Informative

      Don't laugh, Fortran is still widely used in the scientific field. Optimizing compilers such as the SGI/MIPS compilers do good jobs at generating tight code from Fortran. C and C++ are not the easiest things to optimize automagically.

      It's no coincidence that SGI and Cray have excellent Fortran compilers, their customers demand it.

      (sorry I spent all of last Wednesday in 2 seminars with a fellow from SGI's Canadian HPC group, I'm still buzzing. :))

      --
      Trolling is a art,
    2. Re:Superb! by mrm677 · · Score: 1

      Another version of FORTRAN! Yeah! Now if I can just find a card punch machine and reader on eBay, I'll have hutled into the 1970s!

      The state of the art supercomputers in this country, the ASCI machines, primarily run Fortran codes. I would say that half of all new scientific applications are still written in Fortran. Your post isn't funny, its ignorant.

    3. Re:Superb! by StandardDeviant · · Score: 1

      what version of FORTRAN does their compiler support? (I'd check myself but their site is horribly slashdotted.) I've been wanting to learn FORTRAN for a good while, but F77 is a bit of a drag and AFAIK it's the only version supported by a free toolset (g77). (If somebody could point out a free tool(set) that could handle F9x that I'm unaware of, I'd greatly appreciate it.)

    4. Re:Superb! by Anonymous Coward · · Score: 0
      Posting anonymously for obvious reasons...

      I'm a graduate student researching compiler optimizations... I'm not going to refutet that fortran-compiled programs are still in widespread use (although y2k issues replaced a fair amount of fortran code). From a compiler point-of-view, fortran is nasty... keywords can be used for variables, labels, functions, etc, which means it requires a context-sensitive parser. Of course, lexing is also context-sensitive (due to spaces being ignored, except in Hollings strings). A lot of research has gone into context free grammer oparsers, and finite automota, so Yacc/BYacc/Bison and Flex/lex are able to produce superb code, making parsing C code ridiculously faster than parsing fortran code.

      Additionally, well written C code (eg no goto) can be reduced. That's not an option with most production fortran code I've seen.

      Most of the comparisons of C vs fortran were from the early 70s, before the at&t C compiler supported optimization beyond dag-based subexpression elimination, while fortran had 20 years of optimizations applied to it. All recent comparisons of C and fortran show C to produce faster and more optimized code.

    5. Re:Superb! by RV.eq.VFG · · Score: 2, Informative
      If somebody could point out a free tool(set) that could handle F9x that I'm unaware of, I'd greatly appreciate it

      Its not free in the FSF sense but intel do a f95 compiler which is free for personal use on linux (x86 or itanic only).

      The g95 project is developing a free f95 compiler but it is not ready yet: http://g95.sourceforge.net/

    6. Re:Superb! by grondu · · Score: 1

      Hollings strings

      I believe that's Hollerith, not Hollings. I hope Fritz Hollings had nothing to do with them.

      --

      I'm the urban spaceman babe, but here comes the twist... I don't exist

    7. Re:Superb! by afidel · · Score: 1

      The reason Fortran is still used is more of a fluke than anything. Because of the way that Fortran allocates arrays it is not possible for two arrays to overlap in memory so there are certain assumptions in the optimization steps that a Fortran compiler can make that C derived languages cannot make.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  10. GCC performance and another thing... by 00_NOP · · Score: 2, Interesting

    1. GCC: My sense is that it is not a very high performance compiler - is that true? Would a better GCC make a big difference to the free software/oss world?

    2. Does the Watcom WIN32 binary run under WINE?

    1. Re:GCC performance and another thing... by JoshRendlesham · · Score: 1

      The installation program worked fine for me under WINE. The IDE ran as well, but I ran into some problems when trying to compile simple C projects (both from the IDE and command line). My experience with the Watcom IDE and compilers are fairly limited, so it may well be my fault that it wouldn't work.

    2. Re:GCC performance and another thing... by g4dget · · Score: 1

      Depends on the platform. Generally, GNU C/C++ is a good compiler. Sometimes, it lags a bit behind one or the other proprietary compiler for some specific chip (e.g., P4), but it usually catches up quickly. The best way to make it catch up quickly is to come up with specific examples where it could do better--the gcc developers are responsive.

    3. Re:GCC performance and another thing... by FooBarWidget · · Score: 2, Interesting

      "1. GCC: My sense is that it is not a very high performance compiler - is that true? Would a better GCC make a big difference to the free software/oss world?"

      That depends on what you mean by "high performance".
      If you mean how fast GCC can compile stuff, then it's probably not the fastest compiler in this world. Hopefully precompiled headers support will change this.
      But if you mean code speed, then GCC 3.2 is great. It generates code that rivals that of Intel C++.

    4. Re:GCC performance and another thing... by Anonymous Coward · · Score: 0

      The only thing the gcc developers aren't responsive to is the ANSI standard. Well, unless you consider 'extend and embrace' the right response.

    5. Re:GCC performance and another thing... by Anonymous Coward · · Score: 0
      I'm a hot chick. They didn't seem too responsive when i offered to suck them off. Although one of them did ask if i would wear a strap-on and give him a reach around, whatever that is.

      some hot chick

    6. Re:GCC performance and another thing... by Anonymous Coward · · Score: 0

      It generates code that rivals that of Intel C++.

      No, it does not. Intel's C/C++ thrashes GCC in almost every single benchmark (and real-world application) out there. (Too lazy to google, so no link).
    7. Re:GCC performance and another thing... by Anonymous Coward · · Score: 0

      The Intel C++ compiler kicks GCCs ass - there was a news item posted to Slashdot about this recently. You can get massive improvements in kernel performance by using it.

    8. Re:GCC performance and another thing... by be-fan · · Score: 4, Informative

      You mean this link? The one that shows GCC matching Intel C++ 7.0 on everything except the P4 FPU benchmarks?

      --
      A deep unwavering belief is a sure sign you're missing something...
    9. Re:GCC performance and another thing... by Anonymous Coward · · Score: 0

      GCC is fully ANSI-compliant. You get to choose whether it's pedantic (which, I gather, you prefer) or whether it permits the use of extensions.

    10. Re:GCC performance and another thing... by Avakado · · Score: 1

      If you mean how fast GCC can compile stuff, then it's probably not the fastest compiler in this world. Hopefully precompiled headers support will change this.

      If you ever tried compiling applications with GCC on a system withough GNU libc, you would have noticed how important the header sizes are. Compiling applications in e.g. FreeBSD, which uses a small and non-portable C library, is way faster than in Debian or Red Hat.

      --
      The world will end in 5 minutes. Please log out.
    11. Re:GCC performance and another thing... by Anonymous Coward · · Score: 0

      Yes, but he's not running anything to really test it, he should run benchmarks on threaded bins on smp.

      Hell, GCC can't even do static single assignment properly yet.

    12. Re:GCC performance and another thing... by Flywheel · · Score: 1

      1) Yes, the keyword is portability not performance.

      2) I would guess so, but both Linux and FreeBSD has been announced as future goals

      --
      Live long and prosper...
  11. Which to use; WatCom or GNU by one9nine · · Score: 1

    What's the difference between using WatCom's complier and GNU's? How do you make a choice over which compiler to use?

    1. Re:Which to use; WatCom or GNU by jasonditz · · Score: 1

      Well, Watcom's compiler has been one of the best performing for years,

      on the other hand, as the poster originally pointed out 3.22 is a bigger number than 1.0

    2. Re:Which to use; WatCom or GNU by Anonymous Coward · · Score: 0

      Of course, what the poster didn't point out was that Open Watcom 1.0 is also Watcom 11.0c.

    3. Re:Which to use; WatCom or GNU by Meowing · · Score: 1

      g++ compiles modern C++ programs out of the box. Open Watcom 1.0 is still in need of an up to date standard library. I'm sure it will catch up, but it's not quite there yet -- even chokes on a trivial hello word using the current standards.

  12. Performance comparisons by golrien · · Score: 5, Interesting

    I was going to ask if there were any performance comparisons around showing how Watcom performed, but then I realised that anyone with half a brain ran something through Google before Slashdot.

    Win32 compilers (not including Watcom - and with good reason, it's a bitch to set up on Win32)

    as linked from the djgpp FAQ, some info on DOS compilers.

    So, hooray! A lesson in using Google before Slashdot mixed with some blatant karma-whoring.

    PS. this is good too.

    1. Re:Performance comparisons by Anonymous Coward · · Score: 0

      Too complicated. Karma whoring aims lower, with easily digested platitudes. I'd actually have to follow links to mod you up, and that would distract me from contemplating my next hit of crack. You fail.

    2. Re:Performance comparisons by g4dget · · Score: 1
      The choice of optimization flags for GNU C/C++ is pretty simplistic in those benchmarks, and yet it's only about 35% difference in performance. I think the conclusion should be: it doesn't really matter which C/C++ compiler you use.

      One particular issue that comes up again and again is that GNU C/C++ doesn't use inline special functions by default because the Pentium instructions are not standards conformant (they apparently don't give correct results for large arguments). Intel seems to inline those with no hesitation. Any benchmark comparison should probably be run with "-ffast-math", in which case the difference between Intel and GNU C/C++ shrinks to 12%. And I wouldn't be surprised if that remainder weren't due to some other questionable shortcuts Intel is taking.

    3. Re:Performance comparisons by Jeffrey+Baker · · Score: 1

      Wouldn't you consider -ffast-math to be a questionable shortcut? They should rename it -fviolate-ieee.

    4. Re:Performance comparisons by Ninja+Programmer · · Score: 1
      • (not including Watcom - and with good reason, it's a bitch to set up on Win32)
      How is Watcom a bitch to set up? You must be crazy! Its far and away the easiest compiler to set up, or change the install for. The only tricky points is setting up the debugger device, and the environment variables, but those should be done automatically, and is explained completely in the various FAQs and readmes.
    5. Re:Performance comparisons by golrien · · Score: 1

      I just have vivid memories of trying to make the free edition compile something on Windows. I seem to recall in the end, I could make it produce something provided I didn't use the runtime library - but that's why I think of it as a bitch, heh

    6. Re:Performance comparisons by be-fan · · Score: 2, Insightful

      I wouldn't accuse ICC of questionable shortcuts. It's generated code works just great. On the other hand, those benchmarks are quite out of date. GCC 3.2.x is *much* faster than GCC 2.95.x (or GCC 3.1.x for that matter). Instead look at these benchmarks which tests GCC 3.2.1 vs Intel C++ 7.0

      --
      A deep unwavering belief is a sure sign you're missing something...
    7. Re:Performance comparisons by be-fan · · Score: 2, Interesting
      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:Performance comparisons by tonyhill · · Score: 1

      Of course the comparisons were made using gcc 2.95.x (or 2.8 in the second article).

      gcc has come a long way in terms of performance since 2.95.x. 3.2.x now compiles code that runs as fast (or faster, depending on the code) as Intel's C/C++ compiler. Right now, the only reason for me to use Intel's compiler is OpenMP.

      Now, if anyone has made some benchmarks using gcc 3.2.x, I'd be interested. (In fact, I may have to do some on Monday.)

      Tony

    9. Re:Performance comparisons by oxfletch · · Score: 1

      What a crock of shit. You might find gcc 3.2 is faster for some little microbenchmark, but look at this thread for some real world numbers:

      http://marc.theaimsgroup.com/?l=linux-kernel&m=1 04 431408416381&w=2

      Follow it all the way down ... conclusion: it produces slightly slower, rather larger code, and takes much more time to do it.

    10. Re:Performance comparisons by be-fan · · Score: 1

      Um, that's exactly what the Coyote Gulch benchmarks say! The whole point was that GCC's code generation was competitive with Intel's. In my mind, this is offset by the fact that it's slightly more conformant. Nobody claims that it's anywhere near competitive in terms of compilation speed.

      --
      A deep unwavering belief is a sure sign you're missing something...
  13. No Time by Anonymous Coward · · Score: 4, Funny

    Sorry, no time to read this now. Will catch it on the repost....

  14. Who is using Watcom in production? by Anonymous Coward · · Score: 3, Interesting

    Could someone post information on what companies are using Watcom and which products they've built with it?

    This would also be excellent information for Watcom to put on their site. It would give them much more legitimacy.

    1. Re:Who is using Watcom in production? by Anonymous Coward · · Score: 0

      How is this redundant? I see lots of posts talking about comparisons with other compilers but I see virtually nothing about which companies are actually using Watcom to build real life products.

      For me, this crucial information. I'm not going to spend an hour playing around with this compiler if no one else in the world is currently using it successfully in a commerical setting.

    2. Re:Who is using Watcom in production? by Reziac · · Score: 1

      I know that Corel was using Watcom C a few years ago (they converted the WordPerfect codebase into Watcom C when they updated the horrible mess Novell handed them) but couldn't say for sure if they still are. Just looked thru some of their current executables, but whatever Corel is using now, it doesn't leave a compiler signature in the binary. :(

      But I agree, this would be excellent information.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    3. Re:Who is using Watcom in production? by entrigant · · Score: 1

      You mean which companies use to use watcom? id Software comes to mind... made DOOM with it.

    4. Re:Who is using Watcom in production? by RinkSpringer · · Score: 1

      The company where I work for uses Watcom C to compile their software. Their software is specialized controller software which is used for pressbrakes.

  15. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 1, Interesting

    as soon as I can compile and use a good 32bit dos extender with gcc, I will stop wasting my time with watcom. Until then, gcc is not the right tool for my job.

  16. Re:Stop duplication of effort by Anthony+Boyd · · Score: 3, Funny
    This is a waste of time.

    Yeah. That whole "competition" thing is totally overrated.

  17. i have been waiting for this news by zymano · · Score: 1, Informative

    I use the free symantec/digital mars c++ compiler also http://www.digitalmars.com/download/freecompiler.h tml it's good to see alternatives to gcc compilers. One question is what if you use these compilers in commercial software development.

  18. Mainframe compilers by Mainframes+ROCK! · · Score: 2, Interesting

    Has anybody heard any news recently from Watcom/Sybase about the 370 versions of Waterloo C, WATFIV, WATBOL, Pascal, Basic etc?

  19. Re:Stop duplication of effort by selectspec · · Score: 4, Insightful

    What gcc needs is support from the hardware vendors themselves. If the hardware vendos all backed gcc, the would be doing their customers a huge favor giving them the flexibility to move between platforms with greater ease, and reducing build engineers to a single toolset.

    --

    Someone you trust is one of us.

  20. Re:Elegy for the '90s by Anonymous Coward · · Score: 0

    How can this be offtopic? It mentions Watcom twice. That's twice more than most of the posts on this topic.

  21. Re:Hey, let's include a snide comment! by Anonymous Coward · · Score: 0

    I think michael's aside should be moderated "-1 Offtopic". Or "Off-topic" to be grammatically correct.

  22. WX-REXX by Ringlord · · Score: 1

    I used Watcoms WX-REXX on OS/2 (light?)years ago. It was a great product. Now I am a Linux user, but this nearly brought tears to my eyes...!

    Warp speed - I never really got there, but I sur tried!

    1. Re:WX-REXX by Locutus · · Score: 2, Interesting

      Same here and when I saw what VisualBasic was compared to VX-Rexx, I couldn't figure out why Watcom didn't bring VX-Rexx to the Windows platform.

      VX-Rexx was great at quick and dirty applications and prototyping. I remember writing a simple text browser in VX-Rexx when I was building a Java web server. The browser let me write html and push it to the server for testing of the parsing engine.

      If you've not seen it, think of it as VisualBasic on steroids. Hey, it used Rexx for one thing and the function browser was pretty cool for it's day. IMHO.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    2. Re:WX-REXX by Troll_Kamikaze · · Score: 1

      If you've not seen it, think of it as VisualBasic on steroids.

      I hope to God I don't see it anytime soon, then!

  23. Free software not a dumping ground! by leandrod · · Score: 1, Insightful

    Yet another company trying to use free software as a dumping ground for useless software. What does Watcom have to offer today? Which vision of the future they have that could offer something that gcc or something the like cannot?

    I do not see anything they can offer. Even if they had, would it not be better to just release the source code under the GNU GPL and integrate any valuable part into gcc? Thus they could create a new Cygnus based on their gained gcc expertise. But we do not need yet another also-ran, GPL-incompatible, redundant confused-ideas licensed open-source piece software.

    Perhaps some years ago this would have been great. Not it is too little, too late.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
    1. Re:Free software not a dumping ground! by edwdig · · Score: 4, Informative

      The Watcom compiler is the only compiler that supports writing 32 bit code using 48 bit pointers. GCC only supports code where all the segment registers contain the same value.

    2. Re:Free software not a dumping ground! by Anonymous Coward · · Score: 0

      Sybase, or whoever owns it (then) was going to can it, dead. The users suggested they put it out into the public domain. This was YEARS ago and it's taken this long to get to here.

      No, I don't use it anymore, and probably won't, but some will. It's better than not existing, that's for sure.

    3. Re:Free software not a dumping ground! by Ninja+Programmer · · Score: 2, Informative
      • I do not see anything they can offer.
      They offer:
      1. An integrated IDE
      2. Source compatibility with MS VC++
      3. OBJ/Library compatibility with MS VC++ and MASM/TASM/NASM
      4. Compatibility with numerous DOS extenders
      5. A far better "MAKE" than gnumake, Solaris make, or MS's nmake
      6. Open source Win32 compatibility
      7. Inline assembler that uses the proper IA-32 syntax
      I am told, that the sources for the compiler itself are very well structured. I am also told that the sources for gcc are a complete mess.
      • Even if they had, would it not be better to just release the source code under the GNU GPL and integrate any valuable part into gcc?
      The Sybase Open source license protects Sybase. While that's not important to you, it *is* important to Sybase. The open source people have endorsed it as a valid open source license, so that is that.
      • Perhaps some years ago this would have been great. Now it is too little, too late.
      Now on this point you might be correct. However, that remains to be seen.
    4. Re:Free software not a dumping ground! by The+Bungi · · Score: 2, Interesting
      You complain when you don't have participation and when companies refuse to release their products under the OSS model, and then you complain when someone releases software that, in your view, is useless.

      So which is it?

    5. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > The Watcom compiler is the only compiler that supports writing 32 bit code using 48 bit pointers.

      Thanks for the info. How valuable is that?

      > GCC only supports code where all the segment registers contain the same value.

      Given that Watcom has a GNU GPL incompatible license, it will probably be easier to add this capability to gcc if enough talented, available people think it important than bringing Watcom to parity with gcc as to other, more important features as portability.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    6. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > An integrated IDE

      I consider this a misfeature. I want interoperability, not lock-in integration: a compiler is one thing, an IDE is another thing, and I want to choose each as I see fit, not be forced to use a suboptimal combination.

      BTW there are lots of great IDEs, from GNU Emacs on, that integrate just great with gcc.

      As to the other points, they are either debatable or important only for proprietary software compatibility in some cases, or (and) relevant to one obsolete, if still dominant, platform only. I would rather see these features integrated into gcc, but being licensed incompatibly with the GNU GPL robs this code base from any value it could have for me.

      > I am also told that the sources for gcc are a complete mess.

      I wonder who told you that... any real references? gcc is inherently more complex, supporting more languages and platforms. But to achieve this it must be very well structured indeed.

      > The Sybase Open source license protects Sybase. While that's not important to you

      Yes, it is important to me. I like authors being rewarded, and that is what the GNU GPL does with a proper implementation of copyleft. I have not ever seen a better one, and I doubt Sybase has made it. So I guess again a company has been taken over by lawyers who, perhaps with a all too common case of Not Invented Here syndrome, have failed to grab the only license yet that really protects the authors.

      A read at the FSF explanation on weak copyleft by MPL and others might be instructive here.

      > The open source people have endorsed it as a valid open source license, so that is that.

      I consider the whole open source thing a mistake, from moniker to organisation. I am for free software in general and copyleft in particular.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    7. Re:Free software not a dumping ground! by Bobas · · Score: 1

      How valuable? In some sense you might have address space of more than 4G on 32bit machines. Dunno if it doesn't require much involvement to make it work.

    8. Re:Free software not a dumping ground! by leandrod · · Score: 0, Troll
      > You complain when you don't have participation

      Who complains about not having whose participation in what?

      > when companies refuse to release their products under the OSS model

      I could not care less about anything called the OSS model, because that is not well defined and the few fuzzy definitions around do not struck a cord with me. I care about free software, preferrably copyleft.

      > then you complain when someone releases software that, in your view, is useless.

      If I see it as badly done and useless, should not I complain?

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    9. Re:Free software not a dumping ground! by GlassHeart · · Score: 2, Insightful
      Yet another company trying to use free software as a dumping ground for useless software. What does Watcom have to offer today?

      Let's see... a student of compilers picks it up, and learns something. The intangible goodwill encourages another company to open something else. We don't lose another piece of computer history.

      Not every act has to change the world, you know.

    10. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > How valuable? In some sense you might have address space of more than 4G on 32bit machines.

      Given that free software tends to be able to run on more efficient 64 bits architectures, I consider that unnecessary complication. YMMV.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    11. Re:Free software not a dumping ground! by leandrod · · Score: 0, Troll
      > a student of compilers picks it up, and learns something.

      What could he learn there that he could not, probably better, in gcc or a Lisp compiler?

      > The intangible goodwill encourages another company to open something else.

      There are many other, much better, examples. So your point is true but underwhelming.

      > We don't lose another piece of computer history.

      A very uninteresting piece as I see it.

      > Not every act has to change the world, you know.

      Yet not every act should be as shoddy and half-hearted, yet it seems that is so.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    12. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > another [***] gpl zealot

      Not another, but the same that has been advocating copyleft here and elsewhere for years.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    13. Re:Free software not a dumping ground! by 91degrees · · Score: 1

      Given that free software tends to be able to run on more efficient 64 bits architectures

      Well, I'd rather just upgrade my memory than my entire system. I don't need the speed of a 64 bit architecture, but for many apps, lots of memory is nice.

    14. Re:Free software not a dumping ground! by The+Bungi · · Score: 1
      Who complains about not having whose participation in what?

      Well, let's see. The idea -as I understand it- is that *all* software should be free. Right? So you can do whatever you want with it. No? Isn't one of the "problems" the fact that very few companies do this? So why aren't you happy?

      I could not care less about anything called the OSS model, because that is not well defined and the few fuzzy definitions around do not struck a cord with me. I care about free software, preferrably copyleft.

      OK then, "free software". It seems that this Watcom thing is free. You can download it and use it, and stuff. Open source you don't like? What part of them releasing Watcom like this don't you like? Or are you basing you complaint on the technical merits of the thing? Have you used it? How is it "useless"? There are dozens of free/open source window managers out there for Linux. Do you think most of them are useless? Or just the ones you don't like? Would you complain as well if yet another one was released?

      If I see it as badly done and useless, should not I complain?

      If I find it ironic and amusing that you are complaining, should I not point it out?

    15. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > I'd rather just upgrade my memory than my entire system.

      This is not about cheapos gaming systems. 48 bits addressing is only available in expensive Xeon and the like wicked, noisy, energy- and heat-inefficient systems.

      > I don't need the speed of a 64 bit architecture, but for many apps, lots of memory is nice.

      There are other things 64 bits buy you, like a well-engineered, balanced, efficient and robust system, a cleaner architecture.

      Another thing is freedom from both sides of the evil Wintel duopoly. That not even AMD or Transmeta really give you, since they in a way validate x86 as a de facto standard.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    16. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > *all* software should be free. Right? So you can do whatever you want with it.

      Not exactly. I am for copyleft, and that means I should not be allowed to hoard code.

      > What part of them releasing Watcom like this don't you like?

      As I said, not being neither copyleft nor GNU GPL compatible.

      > Or are you basing you complaint on the technical merits of the thing?

      Also. Notice is is limited only to one proprietary platform, that it has not been kept up-to-date, and that it was not viable not even to its vendor.

      > There are dozens of free/open source window managers out there for Linux.

      Actually not exactly for Linux, but for the X Window System on POSIX OSs.

      > Do you think most of them are useless?

      Yes, many are just duplication of effort, me-too or Not Invented Here misguided, ephemerous if idealistic efforts.

      > Would you complain as well if yet another one was released?

      Yes, if it is according to my description above. Even more if it was not copyleft, nor GNU GPL compatible.

      > If I find it ironic and amusing that you are complaining, should I not point it out?

      Perhaps you should know better before pointing out...

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    17. Re:Free software not a dumping ground! by fault0 · · Score: 1

      "I consider this a misfeature. I want interoperability, not lock-in integration: a compiler is one thing, an IDE is another thing, and I want to choose each as I see fit, not be forced to use a suboptimal combination.
      BTW there are lots of great IDEs, from GNU Emacs on, that integrate just great with gcc."

      Simple Question.... do you do any win32 development at all? Nearly all win32 development is done through IDE's, sans ports of UNIX applications.

    18. Re:Free software not a dumping ground! by fault0 · · Score: 1

      > available people think it important than bringing Watcom to parity with gcc as to other, more important features as portability.

      Probably not, as gcc has a pretty obfuscated architecture compared to other compilers, as I imagine OpenWatcom would be much cleaner. Of course, many of the architectural limitations in GCC come from the fact that it is portable, which is not always the best thing to do amongst compilers.

    19. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > Nearly all win32 development is done through IDE's, sans ports of UNIX applications.

      Is that good? I would not say so.

      Anyway, IDEs and porting Unix, or rather POSIX *not* UNIX, applications are orthogonal.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    20. Re:Free software not a dumping ground! by leandrod · · Score: 1
      gcc has a pretty obfuscated architecture compared to other compilers

      With obfuscated you mean modular, flexible, powerful, well-structured and documented, right?

      Or just because you cannot grasp something, then it is obfuscated?

      > many of the architectural limitations in GCC

      Would you care to refer to some, or you just mean it is not yet as fast to compile MS-W32 games as you wished?

      > it is portable, which is not always the best thing to do amongst compilers.

      Why not? Why optimise to one platform only, and then see all the work down the drain? No platform is eternal, and sure enought RMS learned his lesson when he had to migrate from ITS to POSIX.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    21. Re:Free software not a dumping ground! by WzDD · · Score: 1

      >Not another, but the same that has been
      >advocating copyleft here and elsewhere for years.

      Well, I'm glad at least that you're wasting your time posting here rather than doing anything that would actually really further adoption of the GPL. The less we see of that license, the better.

    22. Re:Free software not a dumping ground! by drinkypoo · · Score: 1

      Watcom is portable, it's been on more architectures than nethack. :P

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    23. Re:Free software not a dumping ground! by unsinged+int · · Score: 1

      gcc has a steep learning curve to get past before you can add a new optimization pass or, actually, before you can make just about any modification.

      It is very well documented, portable, etc...but that does not mean the design is easy to deal with as a compiler writer.

    24. Re:Free software not a dumping ground! by Ninja+Programmer · · Score: 1
        • The Watcom compiler is the only compiler that supports writing 32 bit code using 48 bit pointers.

        Thanks for the info. How valuable is that?
      Not very. None of the libraries have been compiled in this mode, as there was no supported OS at the time which supported this kind of memory model.
    25. Re:Free software not a dumping ground! by bluGill · · Score: 1

      Theoritical or real value? Most of the push for 64 but chips is because 32 bits doensn't allow for enough memory. (big databases) The i386 and above supports more than 32 bits (4GB) of memory access, 48bit memory access with a 32 bit computer often would be fast enough.

      There are several areas though where reality gets in the way. No OS that I'm aware of supports this very well, if at all. Segmented memory is tough. Most of us hoped that it went away with the i286 and DOS. Sure it works, but it makes for ugly code, and allows for many subtile bugs.

    26. Re:Free software not a dumping ground! by GlassHeart · · Score: 1
      What could [a student] learn there that he could not, probably better, in gcc or a Lisp compiler?

      How to build a commercially viable compiler. If you're old enough to remember, there once was a time when compilers bragged about how many lines of code they could compile per second, as a significant selling point. This means that compilers of those days (Watcom represented the latter portion of those days) had to worry about compile time as well as run time optimizations, which is a concern that gcc doesn't really have. (In fact, gcc was dog slow compared to Watcom. I've tried it.)

      Have you actually read Watcom code? Since you say "probably", I'll presume you haven't even read it. How the heck do you know that gcc is probably better written?

      A very uninteresting piece [of computing history] as I see it.

      It's almost universally true that people of every time fail to appreciate the historical importance of artifacts of their time. Please learn from history, preserve first, and let our descendants ask the questions. Are you at least an expert in compilers?

      Btw, do you realize that the original Doom game was built using the Watcom compiler? Does the prospect of compiling Doom from source, perhaps 20 years from now, begin to sound interesting?

      Two warning signs of arrogance in your post: dismissing something you haven't seen, and presuming that you know how history will judge. I mean this in the best way possible, so try not to be insulted.

    27. Re:Free software not a dumping ground! by tigga · · Score: 1
      I am for copyleft, and that means I should not be allowed to hoard code.

      Just publish the code.

      > What part of them releasing Watcom like this don't you like?

      As I said, not being neither copyleft nor GNU GPL compatible.

      Oh, your religion is pretty strange. Naming software "free" and limiting it's use is kind of deceiving.. But no worry - playing with words is OK for religious zealots.

      As Stallman put nicely - " Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it."

      So GPL is about getting advantages over other people, right?

      > Or are you basing you complaint on the technical merits of the thing?

      Also. Notice is is limited only to one proprietary platform, that it has not been kept up-to-date, and that it was not viable not even to its vendor.

      So you have not tested it and dislike it out of blue. And regarding proprietary - haven't you noticed? - they plan to port it to Linux and FreeBSD.

      You omitted the word commercially.They said "no longer commerciably viable". It narrows nonviability area, isn't it?

    28. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > Just publish the code.

      Yes, always under copyleft so it remains always free.

      > So GPL is about getting advantages over other people, right?

      It is about denying some people, namely hoarders, unfair advantages over users and authors.

      > you have not tested it and dislike it out of blue

      I dislike first the licensing, and second the me-too, obsoleteness.

      > they plan to port it to Linux and FreeBSD.

      Where we have quite good compilers that could use additional developers and testers instead of duplication of effort. BTW, will they port it to PowerPC as well? That is what I use.

      > You omitted the word commercially.They said "no longer commerciably viable". It narrows nonviability area, isn't it?

      Yes. But then why it is not commercially viable? Would it not be because users refuse to pay for it? There are quite some people willing to pay for gcc, there are even companies set around selling and supporting it.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    29. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > you're wasting your time posting here rather than doing anything that would actually really further adoption of the GPL

      Not everyone is a coder.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    30. Re:Free software not a dumping ground! by leandrod · · Score: 1
      How to build a commercially viable compiler.

      Such as gcc, for example? There is more than one company making good money for many years now selling and supporting it.

      > there once was a time when compilers bragged about how many lines of code they could compile per second, as a significant selling point.

      On which platform? Watcom may be fast, but it cannot compile for embedded platforms, nor for big iron. Now what is easier, to speed up gcc or go generalise Watcom?

      > How the heck do you know that gcc is probably better written?

      See how many years it has been in existence, with so many front-ends, on so many platforms, targetting so many others, maintained and improved by so many people. Watcom could not even be released as was.

      > Does the prospect of compiling Doom from source, perhaps 20 years from now, begin to sound interesting?

      No. Much better if Doom is made standards-compliant. BTW it probably is already, or would not be available in so many platforms.

      > dismissing something you haven't seen

      Why is so much reporting and reviewing done if you think everyone is supposed to see and touch before reflecting?

      > presuming that you know how history will judge

      You seem to from the whatever is, is good school. I am for the common good.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    31. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > Most of the push for 64 but chips is because 32 bits doensn't allow for enough memory.

      Not only. I do not care so much for 64 bits in my desktop, for example, but appreciate being able to use a more efficient RISC processor. It helps that when I need 64 bits the migration path will be straightforward.

      > No OS that I'm aware of supports this very well

      Precisely. Why use an ugly hack instead of the real thing?

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    32. Re:Free software not a dumping ground! by leandrod · · Score: 1
      > Watcom is portable, it's been on more architectures than nethack.

      References?

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    33. Re:Free software not a dumping ground! by Anonymous Coward · · Score: 0

      Have you heard of FreeDOS? This will mean a TON to them. You GPL folks are a bunch of whining pussies.

    34. Re:Free software not a dumping ground! by Anonymous Coward · · Score: 0
      Precisely. Why use an ugly hack instead of the real thing?

      Because you can't find a girl that will spread her legs for you, but you have 2 hands.

    35. Re:Free software not a dumping ground! by Anonymous Coward · · Score: 0

      Those that can't code, harp upon the release of others code apparently.

      I mean, if you were a coder, hell, you would never get anything done.

      While...
      1. Write a line.
      2. Call RMS to bless it.
      3. Kiss RMS 4SS.
      4. Post to slashdot.
      return;

    36. Re:Free software not a dumping ground! by GlassHeart · · Score: 1
      There is more than one company making good money for many years now selling and supporting [gcc].

      You're beginning to run off a tangent for the sake of argument, so let me remind you how we got here. I asserted that reading Watcom code could be interesting to a student, because it was a real live commercial product at its time. Whatever merits or commercial potential gcc has is not relevant, because free software doesn't compete on the same terms.

      Now, obviously, such a student should also go ahead and study gcc.

      Much better if Doom is made standards-compliant.

      Ahh, so now you know what a computer archaeologist would want, twenty years from now? Are you really so sure that she would not rather run the original build on a cycle-accurate 80386 emulator?

      Why is so much reporting and reviewing done if you think everyone is supposed to see and touch before reflecting?

      I certainly don't insist that you have firsthand knowledge of everything you speak of. Can you cite a reputable review or report of gcc's or Watcom C's code quality that you've read before posting? In fact, your evidence of gcc's quality consists of:

      See how many years it has been in existence, with so many front-ends, on so many platforms, targetting so many others, maintained and improved by so many people.

      which is entirely circumstancial. As Linus Torvalds himself will admit, a microkernel design would be "nicer" in theory. However, Linux is hugely successful despite or because it is monolithic. Success in the "marketplace" is a result of many, many factors, sometimes despite poor design.

      You seem to from the whatever is, is good school. I am for the common good.

      I won't even try to understand what that means. All I will say is that the release of Watcom source code is a good thing, if it only preserves a snapshot of software engineering in the early 1990s. Pooh-poohing efforts like this, when it's already so easy for a failing company to bury its code forever, helps us lose irreplaceable portions of our history. Even examples of terrible code is worth saving, because it's history.

  24. GCC by mark_space2001 · · Score: 4, Informative
    I'm with michael on this one. There are a lot of free compilers out there now, including Microsoft VC++ and Borland

    Gcc is good, open, and could use some work, so please think about helping out. My favorite is MinGW which is a really nice and decently maintained Win32 version of gcc and binutils. MinGW also distributes MSYS which is a bash shell and other gnu utilities that make a windows box capable of running a Linux configure script. This allows much easier porting of GNU applications to windows and vice versa. There are several GUI compilers based on MinGW too, see the web page FAQ. A nice GUI GCC based compiler for Win32 is Bloodshed Dev-C++, which I've used.

    Cygwin is good too but I prefer MinGW (obviously).

    So think about helping out, our tools will only get better if folks work on them.

    1. Re:GCC by ryanr · · Score: 1

      Since when is VC++ free? What you linked to is the .net SDK download... does that include a compiler?

    2. Re:GCC by Senjutsu · · Score: 1

      What you linked to is the .net SDK download... does that include a compiler?

      Click the link:

      The Microsoft® .NET Framework Software Development Kit (SDK) includes the .NET Framework, as well as everything you need to write, build, test, and deploy .NET Framework applications--documentation, samples, and command-line tools and compilers.

    3. Re:GCC by The+Bungi · · Score: 2, Informative
      Yes. It includes the C#, VB.NET and JScript.NET compilers, as well as the C and C++ compilers, along with the up to date libs and headers.

      This is surprising (was to me), because although the MS linker had been available previously with the Platform SDK, the compiler itself had never been (the libs and headers were).

      The .NET compilers have to be present in any .NET-based environment, so they have no choice but to ship them. But the C++ compiler does not. I'm not sure why they're doing this now, but hey.

      In fact, there are a couple of projects now trying to get together a free front end/IDE for the compiler, although I'm not sure if that violates their EULA. There are free/open front ends for C# (SharpDevelop and WebMatrix) available today, of course.

    4. Re:GCC by ryanr · · Score: 1

      I had clicked it... I didn't see the bit you just highlighted, I guess. So, that's cool.. you can get the command-line compiler stuff. I think this is also the first time one now could release some MS C code made with MS tools, and be sure that everyone out there could build it without having to buy something. It's not the same as VC++ though, is it? Sounds like it's missing the IDE.

    5. Re:GCC by brunes69 · · Score: 1
      I'm with michael on this one. There are a lot of free compilers out there now, including Microsoft VC++ [microsoft.com]

      Last I checked,the MS VC++ compiler ran you over 1000 dollars for the basic version or 549 for an upgrade. The .Net development kit you point at only has a C# compiler for .Net, it can't make native executables.

    6. Re:GCC by mark_space2001 · · Score: 1

      I've never actually downloaded that package. It's from a list of free C++ compilers, the same one I got the Borland link from.

      I'm taking someone else's word that there is a command line version of VC++ in there somewhere. If I'm wrong, *shrug* I use MinGW anyway. ^_^

    7. Re:GCC by chrisseaton · · Score: 1

      I'm looking at the program folder now and it includes the C++ compiler which compiles to native and .NET managed.

    8. Re:GCC by Anonymous Coward · · Score: 0

      The full enterprise edition of VC++ 6.0 is expensive. But the "Standard" edition is about $100.

    9. Re:GCC by rabidcow · · Score: 1

      Note that the free compiler included with the SDK does not do all the optimizations that make the vc7 compiler worth getting.

      ommand line warning D4029 : optimization is not available in the standard edition compiler

    10. Re:GCC by istartedi · · Score: 1

      In fact, there are a couple of projects now trying to get together a free front end/IDE for the compiler

      Don't just build an IDE for *one* compiler. Build a generic IDE that will work with any compiler, and use an XML-based config file to generate the dialog boxes that map to the command-line options for the compiler. It's something that I've wanted because I anticipate moving from Windows to MacOSX and/or *NIX at some point and I'd like to be able to use the same IDE and have the project files and everything work seemlessly regardless of the OS or the compiler. Yes, of course there will be some differences between compilers, but for the most part those differences can be mediated through the config files.

      Also, build a generic IDE that doesn't target a MSFT product and they have a much harder time arguing that it's an attempt to violate their EULA.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    11. Re:GCC by cygnusx · · Score: 1

      The WebMatrix IDE (for ASP.NET) which the grandparent post mentioned was developed by Microsoft employees. I don't think they are worried it'll be competition for VS.Net anytime soon.

  25. Re:Who needs C++ anyway? by Anonymous Coward · · Score: 0
    You're right, he does suck!

    "I don't know anything about concurrent
    programming or C++. Also, I like to take
    it in the ass..." - Rupert Pigott on comp.arch. 5/22/2002

  26. Re:Stop duplication of effort by Anonymous Coward · · Score: 0

    Competition is the soul of slashdot. That's why they duplicate-post stories.

  27. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 1, Interesting

    if you ever have to code a real time application chances are DOS is among the possible choices if you want to base it on x86 hardware. so watcom would be a good DOS compiler. it was the best back then in 1996, it should be now, as DOS tipped over prior to that and all other compiler development with it.

  28. Watcom Memories by Lucas+Membrane · · Score: 2, Insightful
    The IDE's that Watcom had were refreshingly different. Their C++ IDE was good, but when they upgraded the C++, they came out with Power++, which was a very nice RAD product, but it was too buggy. If the compilers are cleaned up and they open source the IDE's too, this might be of value.

    What killed them? Did they pull all their brains off C++ to work on PB? Was competition from MS too tough? Was their GUI builder (licensed from some 3rd party) too lame? Was the cost of implementing the C++ standard too high? (Watcom was late to offer STL -- they included their own (way different) libs instead.)

    We were a couple of generations back on chips when Watcom pretty much stopped pushing their compiler technologies. I wonder how much they lose by not having optimizations targetting new hardware features.

    1. Re:Watcom Memories by Locutus · · Score: 4, Informative

      What killed them? If you remember when this all was happening, Microsoft was out to take over C++ and all the companies who did cross-platform frameworks were attached in standard MS style. Monopoly money funded subsidizing of their Visual C-- product and MS-MFC. Then when Watcom wanted to include MFC with the Watcom C++ compiler package, Microsoft said that would only happen if ALL other frameworks on the CD were removed. Remember, Watcom C++ shipped with DOS16, DOS32, Win16, Win32c, Win32, OS/2-16, OS/2-32 compilers with the IBM OCL framework and some others like Zinc if I remember correctly.

      Watcom would have to eliminate all the support for the other platforms to license MFC and ship it with their compilers. And Microsoft was all but giving Visual C-- away at the time also.

      The Watcom compiler was one of the fastest on the market from what I remember. I had heard that IBM used it for the WinOS/2 subsystem on OS/2 to make it a faster Windows than Dos/Windows.

      Think about it, Microsoft HATES anything that abstracts the Win32 API and crossplatform frameworks and crossplatform compilers where one of the early targets of the beast in Redmond. Borland was the only one that got any money out of taking Microsoft to court for attacking it's business using illegal means. The others were too small and just folded and looked for other ways to make a business.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    2. Re:Watcom Memories by Anonymous Coward · · Score: 0

      WATCOM C/C++ compiler was never fast. Very slow in fact but it's beauty is that it produced very nice and fast code. You could run disassembler on it and would say Wow! Nice assembly programming.

      If you needed fast compiler enter the Borland family. Turbo C/C++, Borland C++ was compiling projects way faster then anything else, because they really were turbo.

      The Microsoft compilers were weird bunch. They were slowly compiling the slow code. :-)

      Another excellent feature of WATCOM C/C++ is the cross platform development. You could compile pretty much for any major OS on x86 processor.

      But then again where are the Borland and WATCOM now and what happen to Microsoft.

  29. Or if you prefer, gcc is up to 3.2.2. by Anonymous Coward · · Score: 0, Offtopic

    You could use http://censorware.org/, or if you prefer, http://censorware.net/, which is not the hands of a dirty squatter.

  30. With apologies to Sonny Bono by Anonymous Coward · · Score: 0

    (With apologies to Dr. Seuss)

    Ever since the Eldred decision, I have boycotted Dr. Seuss Enterprises, who submitted an amicus brief in favor of the Bono Act.

    1. Re:With apologies to Sonny Bono by Anonymous Coward · · Score: 0

      Then I rescind the apology.

      Or more correctly, make it "With apologies to Theodore Geisel". He's not responsible for that brief, the company is (after his death).

      The parent post was intended as on-topic satire on tech companies releasing moldy old code under semi-free licences, btw. But the "Offtopic" mod is much more satisfying. Is there a /. editor using unlimited mods on this story? There seem to be many more "Offtopic" mods than usual, and many of them the crack-smoking kind (like the question about 370 mainframe compiler code, which would arguably be more useful than what they did release).

  31. Which compiler ignores architectures? by yerricde · · Score: 1

    gcc ... ignores some architectures completely.

    Watcom C++ ignores ARM, MIPS, PowerPC, and SPARC completely because Watcom C++ is an x86 compiler.

    --
    Will I retire or break 10K?
  32. I liked the old commercial versions by Anonymous Coward · · Score: 0

    I worked at companies that used Watcom for years. The reason that we chose to use it was it generated much smaller code than any of the alternatives. We always got good support from Watcom - we got to talk with the wngineers on the phone.

    Now there aren't many commercial alternatives to MS in the PC C/C++ space. I think the only other PC C/C++ compilers are from Intel and Borland. Since the last (two?) major upgrade of MS C/C++ came from purchasing another companies compiler, I wonder how long the next upgrade will take?

    1. Re:I liked the old commercial versions by Valafar · · Score: 1

      You over looked Metrowerks CodeWarrior. It's a great compiler for both x86, PPC, Palm and irrc, Playstation.

  33. Sure it is by Planesdragon · · Score: 4, Insightful

    Yet another company trying to use free software as a dumping ground for useless software.

    Maybe you're not up to snuff on the philosiphy of code-reuse and what Free Software means.

    If software and code is a commodity, and the value then becomes it configuration/customization, then every little bit of trash that can be opened is a Very Good Thing. If the company was proprietary their entire corporate life, but releases the soruce as GPL (or BSD) when they fold, this is a Good Act and should be Lauded and Welcomed and Thanked.

    The darn site's /.'ed--but as long as they use a GPL-compatbile license, there's nothing stopping the GCC folks from pouring over OpenWalcom for anything useful.

    1. Re:Sure it is by leandrod · · Score: 1
      > Maybe you're not up to snuff on the philosiphy of code-reuse and what Free Software means.

      Yes I am. I guess I know more than you, in fact. Can you tell me why do you think otherwise?

      Now seriously, back to objective, non-personal stuff...

      > If the company was proprietary their entire corporate life, but releases the soruce as GPL (or BSD) when they fold, this is a Good Act and should be Lauded and Welcomed and Thanked.

      What they did was neither GNU GPL, nor BSD, nor compatible with GNU GPL. Perhaps not even with unmodified BSD, practically speaking, due to BSD having that obnoxious advertising clause...

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    2. Re:Sure it is by The+Bungi · · Score: 1
      [...] Perhaps not even with unmodified BSD, practically speaking, due to BSD having that obnoxious advertising clause...

      Holy crap. Are you RMS' lost child? Do you plan on holding that over BSD's head forever and ever and ever?

    3. Re:Sure it is by leandrod · · Score: 1
      > Do you plan on holding that over BSD's head forever and ever and ever?

      Should not I? Unmodified BSD licensing is incompatible with GNU GPL, and actually impractical for commercial software that needs to be advertised. I have nothing against fixed BSD licenses, other than being open to hoarding. I know some authors prefer it like that, but I lament it.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    4. Re:Sure it is by The+Bungi · · Score: 1
      Unmodified BSD licensing is incompatible with GNU GPL

      You keep saying that like it's some sort of requirement for software to even exist.

      other than being open to hoarding

      And you keep saying this like it's somehow akin to hoarding food during a civil emergency or something.

      Get over yourself.

    5. Re:Sure it is by leandrod · · Score: 1
      > You keep saying that like it's some sort of requirement for software to even exist.

      Not so. Yet the world would be a nicer place as I see it. Feel free to differ.

      > you keep saying this like it's somehow akin to hoarding food during a civil emergency

      That is just your over-sensitiveness.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    6. Re:Sure it is by Richard_at_work · · Score: 1

      Diddums. My heart bleeds.

    7. Re:Sure it is by yomegaman · · Score: 1

      I don't know if the Watcom license allows relicensing as BSDL, but I can't imagine how the advertising clause would prevent it. That only kicks in when you incorporate code already licensed under BSDL, right? Also, wasn't it removed awhile ago anyway?

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    8. Re:Sure it is by Anonymous Coward · · Score: 0

      Actually, I would think if you Free Software was so important to you that you would at least know what you were talking about. The advertising clause was removed quite a while ago.

      FYI: I also think your groupthink and general mindlessness are quite compatible with the Free Software ideals. Good job!

    9. Re:Sure it is by leandrod · · Score: 1
      > The advertising clause was removed quite a while ago.

      Yet many still use the unmodified rather than the fixed BSD license. Some do not even have a choice, because forked before the clause was removed.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    10. Re:Sure it is by leandrod · · Score: 1
      > I don't know if the Watcom license allows relicensing as BSDL

      Relicensing actually means adding restrictions. So one can take the modified BSD license and relicense it under the GNU GPL, but the same is not true for the original BSD license.

      > I can't imagine how the advertising clause would prevent it.

      The FSF enlightens ye!

      > wasn't it removed awhile ago anyway?

      Yes, but code licensed under it is still floating around.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    11. Re:Sure it is by yomegaman · · Score: 1

      I'm not talking about whether BSD-licensed code can be relicensed as GPL, I'm talking about whether code under the Watcom license can be relicensed under BSDL. You claimed that the advertising clause prevents the latter, but I just don't see how that can be so.

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    12. Re:Sure it is by Anonymous Coward · · Score: 0

      I think he has been raised on too much RMS teet milk.

      He has that same "head dizzying" lack of logical follow through that RMS is prone too.

      "If it ain't perfect, stone it." seems to be the cry of the RMS fanatics. "Nothing but pure for us. Unless the High Priest of the GNU, RMS, blesses it, it is accursed."

    13. Re:Sure it is by Planesdragon · · Score: 1

      Yes I am. I guess I know more than you, in fact. Can you tell me why do you think otherwise?

      Because you were complaining about someone Opening their code. Open--even a LITTLE open--is better that totally closed.

      If we could pass a law that required any company EOLing a piece of software to that was sold in the past 18 months (or even longer--5 years, or 10, or 20...) to Public Domain their code, the world would move step closer to the Free Software ideals.

      What they did was neither GNU GPL, nor BSD, nor compatible with GNU GPL. Perhaps not even with unmodified BSD, practically speaking, due to BSD having that obnoxious advertising clause...

      Well, shoot. There goes the code-mixing benefit. But at least it's better than nothing.

    14. Re:Sure it is by leandrod · · Score: 1
      > I'm not talking about whether BSD-licensed code can be relicensed as GPL, I'm talking about whether code under the Watcom license can be relicensed under BSDL.

      Can't, because the Watcom license carries restrictions that aren't present in BSDL. Remember, "relicensing" isn't relicensing in fact, it is just adding restrictions. You can't remove a license and replace with another.

      > You claimed that the advertising clause prevents the latter, but I just don't see how that can be so.

      Sorry, I just misread you. The effect is the same, but not from that cause.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  34. In Colonial Boston... by Anonymous Coward · · Score: 0

    ...they don't konw what open watcom 1.0 is, or know about computers for that matter.

  35. Now all we need.. by jericho4.0 · · Score: 1
    Now all we need to see is Intel releasing their compiler. As other posts have mentioned, gcc could use some optimization improvments, and Intel has em.

    It's been a long time since I've used the Watcom compiler, but it used to be the bomb. I use gcc exclusivly now, and sometimes pine for the day when a build was done in seconds instead of minutes. I'm betting it will be a difficult undertaking to incorprate the Watcom code, though.

    --
    "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
    1. Re:Now all we need.. by g4dget · · Score: 1
      gcc could use some optimization improvments, and Intel has em.

      I'm not so sure. In many of the benchmarks I have seen, differences have been to questionable optimizations by the Intel compiler; often, you can enable the same optimizations in GNU C/C++ if you like, but they aren't on by default.

      I suspect that GNU C/C++ might see some improvements in P4-specific optimizations, but they are going to happen.

      In general, the best way to help GNU C/C++ to improve is to do benchmarks and track down performance bottlenecks. Throwing out GNU C/C++ for Intel C++ won't be a good solution in the long run.

    2. Re:Now all we need.. by Anonymous Coward · · Score: 0

      I'm betting it will be a difficult undertaking to incorprate the Watcom code, though.

      Don't you mean 'assimilate' the Watcom code?

      Nice little borgie... (reaching for rock)

    3. Re:Now all we need.. by Anonymous Coward · · Score: 0

      Oh but they do have a free FOR NON COMMERCIAL USE linux compiler. They have 30-day trials for the rest of them.

      http://www.intel.com/software/products/compilers /c lin/noncom.htm

      That's the linux compilier, the windows version is only 30-day trial.

    4. Re:Now all we need.. by JoeBuck · · Score: 1

      Benchmarks are showing Intel beating gcc by an average of 10 to 15 percent, though there are some cases where Intel's compiler is twice as fast, and a few where gcc wins. On average, Intel does better, but the difference is not huge.

    5. Re:Now all we need.. by MikeBabcock · · Score: 1

      I wouldn't mind AMD taking on a similar project. Perhaps each submitting a GPL'd compiler to the GCC group would get us a good blended optimizing compiler?

      I use AMD's Code Analyst tool with VC++ 6.0 when on Windows and its quite helpful.

      --
      - Michael T. Babcock (Yes, I blog)
    6. Re:Now all we need.. by cimetmc · · Score: 1

      AMD is helping the GCC project by funding the development work to include support for 64bit AMD processors and improve support for other AMD processors as well. The work is actually carried out by GCC specialists from Suse, but AFAIK, AMD is at least partly paying for this.

      Marcel

  36. Re:Stop duplication of effort by Anonymous Coward · · Score: 0

    When was gcc at the leading edge? Compared to what?

  37. Re:Watcom was great. How about today? by CresentCityRon · · Score: 1

    So its the primary toolset for DOS work these days? If so I guess that is far and away from Sybase's meat and potatoes.

  38. Re:Stop duplication of effort by Ninja+Programmer · · Score: 1
    • I'm looking forward to someone benchmarking gcc vs watcom to see how they do.
    Well, I'll save you the effort -- gcc will crush WATCOM C/C++ on pure C or C++. Bleeding edge performance is not what is being offered with the current WATCOM C/C++. But to tell the truth (as you indicate as well), gcc is not bleeding edge performance either.

    Fixing the compiler performance requires a look at the fundamental code generating mechanisms of the compiler itself. On this point, having a cleaner and more easily understandable architecture is more important that the current snap shot of its performance. And on this score, I think I am told WATCOM C/C++ is somewhat ahead of gcc.
  39. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 0

    It doesn't have the obnoxious GPL. Perhaps we can even get NetBSD to compile with Watcom C in the near future, so we can ditch the GNU mess entirely, except for those few small GNU utilities that are essential, like 'less'.

  40. YAOSL by _|()|\| · · Score: 1
    If the company ... releases the source as GPL (or BSD) when they fold, this is a Good Act ... As long as they use a GPL-compatbile license, there's nothing stopping the GCC folks from poring over OpenWalcom for anything useful.

    As the parent post said, it is GPL incompatible. You can view it at the OSI site.

    While I'm not one to sniff a gift fish, it's disappointing to see yet another "open source" license that will relegate Open Watcom to abandonware.

    1. Re:YAOSL by Planesdragon · · Score: 1

      As the parent post said, it is GPL incompatible.

      OK, there goes the "code re-use" and "contribution to the cause" benefits.

      But it still lets those who use Walcom use it, forever, and update it themselves as needs be--which was, after all, the original flash point for Free Software.

  41. What happened to Watcom by Anonymous Coward · · Score: 5, Informative

    Just wondering what they(watcom) are up to now.

    IIRC: Watcom was purchased by Powersoft. Powersoft's main product was a front-end database tool called PowerBuilder. One of Watcom's products was a small database called Watcom SQL. Powersoft bought Watcom so that they could ship Watcom SQL along with Powerbuilder, so that Powerbuilder could run OOTB.

    Oddly enough, Sybase bought Powersoft a few years later so that they could use Powerbuilder to compete against Oracle's front-end tools. This meant Sybase ended up with Watcom's assets, even though they were not particularly interested in them.

    1. Re:What happened to Watcom by mobiGeek · · Score: 2, Interesting
      Oddly enough, Sybase bought Powersoft a few years later so that they could use Powerbuilder to compete against Oracle's front-end tools. This meant Sybase ended up with Watcom's assets, even though they were not particularly interested in them.

      And to continue the story...

      1. Sybase bought Powersoft in 1995.
      2. The "Watcom" group, still based in Waterloo Ontario, became the Mobile And Embedded (MEC) division of Sybase.
      3. In 2000, Sybase spun the MEC division off as its own company: iAnywhere Solutions Inc.

      iAnywhere makes the very powerful, popular (and developer friendly!) SQL Anywhere Studio as well as other products.

      See more:

      Caveat: I might have some biases...
      --

      ...Beware the IDEs of Microsoft...

  42. relaxxxxxx....... by Anonymous Coward · · Score: 0

    i knew it was ignorant and STILL found it funny

  43. Re:Hey, let's include a snide comment! by larry+bagina · · Score: 0, Offtopic

    Seriously. Of course, micheal also uses windows 98 because it's 95 versions ahead of linux 3, and 85 versions ahead of OS X.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  44. No, actually by exp(pi*sqrt(163)) · · Score: 4, Interesting
    Intel have a long history of claiming that they produce a fast compiler, after all they know the Intel specs. However I have never found this to be true over the last 7 or 8 years (I think it was called Proton years ago). I am not sure I have found any code that is significantly faster compiled with the Intel compiler and have found much that is slower. I haven't tried v6 of their compiler though. Maybe, just maybe, they've now picked up some tricks from the KAI guys.

    Incidentally, vectorization in Intel C/C++ is a joke. I put so many hints into my code (aligned variables, processed stuff in suitable sized chunks etc.) and still couldn't trigger the compiler to vectorize. It's much easier to insert SSE instructions yourself.

    The Intel compiler has better error reporting than MSVC++. I use it when I don't understand why MSVC++ is barfing on my template code. This is more useful than it sounds!

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    1. Re:No, actually by be-fan · · Score: 1

      Ugh. You use VC++ for template code? I feel for you. But I second the Intel error message thing. The EDG frontend has the best error messages around. GCC's has improved in 3.2, but I still use ICC to compile when I can't find out what's wrong.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:No, actually by Dr.+Sp0ng · · Score: 1

      The Intel compiler has better error reporting than MSVC++. I use it when I don't understand why MSVC++ is barfing on my template code.

      MSVC++'s problem with templates goes far beyond simply not reporting the error well - its template support is crappy, and just plain does not follow the C++ specifications. VC++ 6 doesn't even support partial specialization, which are somewhat of a key feature of templates (supposedly VS.NET is better but still not quite there).

    3. Re:No, actually by Aart+Bik · · Score: 1

      Would you mind sharing some examples of code where the Intel compiler misses obvious opportunities for vectorization, since I find your claim rather strong (also considering the fact that you have not even tried version 6.0 yet; verions 7.0 is already out now)? A recent article with programming guidelines for vectorizing compilers that you may find useful can be found at: http://www.cuj.com/articles/2003/0302/0302c/0302c. htm?topic=articles Privately I maintain a web page with some more in-depth information on vectorization for SSE/SSE2. See: http://www.aartbik.com -- Aart Bik, Senior Staff Engineer, Intel Corporation email: aart.bik@intel.com

    4. Re:No, actually by Anonymous Coward · · Score: 0

      Since when does Microsoft support *anybody's* specifications?
      Gotta have that one degree of separation ;-)

    5. Re:No, actually by Ninja+Programmer · · Score: 2, Informative

      Most people who have looked into this have not found your claim to be true. The Intel compiler *does* produce better code on average. I will agree with you about the code vectorization of the Intel compiler except for the very latest version of it which has actually shown itself to vectorize pretty much any time there is a reasonable opportunity for it.

    6. Re:No, actually by jericho4.0 · · Score: 1
      Ya know, the last thing anyone needs when talking shit on /. is a/the(?) "Senior Staff Engineer" of Intel showing up to call them on it. :-)

      Seriously, as I hinted at in the OP, I think the Intel compiler rocks. Can you share anything about future plans for the source? After all, Intel is a hardware company, no?

      Even a fully disclaimed, 'not my employers opinion', opinion would be interesting.

      --
      "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
    7. Re:No, actually by Aart+Bik · · Score: 1

      No it is "a", not "the" although seeing Intel's vectorization being called a "joke" became rather personal :-) As for any future plans, I am the wrong person to ask. I am just vectorizing loops here....

    8. Re:No, actually by exp(pi*sqrt(163)) · · Score: 1

      Wait until Monday! The most trivial vectorizable loop generates the message that the loop couldn't be vectorized. As for versions 6 and 7, I've heard the story about future versions many times now.

      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    9. Re:No, actually by exp(pi*sqrt(163)) · · Score: 1
      Most people who have looked into this have not found your claim to be true
      I am surprised. My experience with the Intel compiler spans many years with many different types of code ranging from plain ordinary C to highly generic C++ code, from fluid dynamics to string processing. My work colleagues and my friends report the same. I can test it quite easily because it's a simple matter of checking one checkbox, recompiling and timing. I got bored of it eventually.
      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  45. Re:Watcom? by Anonymous Coward · · Score: 0

    True story: the company was originally named "Watcock". It was changed when some of the male engineers felt that name cast aspersions on their manhood. So you're not fair off the mark (well, in gender terms you're about as far off as you could be, but you know what I mean).

  46. What's wrong with violating IEEE in some cases? by yerricde · · Score: 1

    [The GCC team] should rename [GCC's -ffast-math optimization flag] -fviolate-ieee.

    Or how about -fthis-is-a-game-not-scientific-research -fdont-give-two-poops-if-its-half-a-pixel-off ?

    --
    Will I retire or break 10K?
    1. Re:What's wrong with violating IEEE in some cases? by nusuth · · Score: 1

      Add -fthis-program-has-no-bugs and you are done. Fastmath does questionable optimizations with valid input but its real danger lies in how gracefully it catches and handles invalid input (not at all.) It is not worth the trouble.

      --

      Gentlemen, you can't fight in here, this is the War Room!

  47. Try DJGPP by yerricde · · Score: 1

    as soon as I can compile and use a good 32bit dos extender with gcc

    As soon as now.

    --
    Will I retire or break 10K?
  48. Oh, and *I'm* Ignorant? by occamboy · · Score: 0, Flamebait

    I suppose that writing in FORTRAN is marginally better than writing in C or Assembler. But... there really are better options: I base this on 20+ years of writing sucessful applications using a range of platforms and languages. (And I'm an EE orignally, have designed ICs, so I think I know a bit about technical applications).

    I suppose that the continued proliferation of FORTRAN is a symptom of why the pace of significant new scientific discovery has dropped off tremendously in the last 20-30 years. No major medical breakthroughs -- we've made almost 0 progress in curing cancer, a little in curing heart disease. No major breakthroughs in physics that I can recall.

    The only real advances have been in technology -- and technology industries don't use FORTRAN, to my knowledge.

    1. Re:Oh, and *I'm* Ignorant? by entrylevel · · Score: 1

      I suppose that the continued proliferation of FORTRAN is a symptom of why the pace of significant new scientific discovery has dropped off tremendously in the last 20-30 years.

      I'm usually not one to argue semantics, but I really can't tell what you are trying to say here. How can one thing be "a sympton of why" something else (passive tense of some verb)? What does that mean? Do you mean that the proliferation of FORTRAN is a symptom of the slow pace of scientific breakthroughs or are you blaming the slow pace of scientific breakthroughs on FORTRAN?

      I realize after reading it to myself that this may sound like a grammar troll, but as someone with only a tiny bit of real world experience with FORTRAN, and no experience (aside from what I see/hear/read in the news), but plenty of interest in the scientific community, I am genuinely curious as to what you meant.

      --
      Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
    2. Re:Oh, and *I'm* Ignorant? by occamboy · · Score: 1

      I was (too-subtly) alluding to my belief that the use of FORTRAN (a generally ridiculous tool to use these days) represents a symptom of an underlying disease: the intellectual vacuum that has proliferated in science. Years ago we had some smart folks. Now we have institutionalization, greed, lack of accountability, and general BS.

      Try a little experiment: read a scientific paper from 30 or 40 years ago. It will likely be concise, readable, and thoughtful, with a real statement at the end that tells the reader the findings and the significance. Now read a scientific paper from the last 10 years. It will typically be incomprehensible, filled with faulty statistics, and will invariably end with some vague and meaningless statement of the findings, or lack thereof.

      Argh!

    3. Re:Oh, and *I'm* Ignorant? by Anonymous Coward · · Score: 0

      I suppose next you're going to tell me that Fortran caused the Dark Ages. Really, that was the stupidest post I've read for a long while.

    4. Re:Oh, and *I'm* Ignorant? by Anonymous Coward · · Score: 0

      The use of Fortran rather than C for scientific computing is due to the fact that numeric code is frequently faster in Fortran than in C. This is because prior to C99 there's no standard way to tell a C compiler that arrays passed in as pointers don't alias each other, so there is much less possibility for optimization.

    5. Re:Oh, and *I'm* Ignorant? by Anonymous Coward · · Score: 0

      Hey man it's publish or perish so a lot of bull has to get published.

      My main academic interests are in the humanities so trust me i know bull when i see it.

      It's true though, go take any academic journal and read it, most of it is stupid fluff that contributes nothing.

      These days every tom, dick and abdul can get a masters or phd just so long as they jump through the correct hoops and have the cash to pay the bills.

  49. "Open source" is clearly defined by yerricde · · Score: 1

    I could not care less about anything called the OSS model, because that is not well defined

    If this document doesn't precisely define open source, what is it lacking?

    --
    Will I retire or break 10K?
    1. Re:"Open source" is clearly defined by leandrod · · Score: 1
      > If this document doesn't precisely define open source, what is it lacking?

      Perhaps I should have been clearer, more precise.

      I know about the OSD and agree it defines open source precisely. But what is meant by OSS model, which was the expression I complained about? When people speak like that, they can have any number of thing in their mind, from better software to price to being able to read source, but seldom freedom.

      To me it is just like speaking about OO data model. It does not exist as such, yet makes people who failed to learn the real thing (in this example, the relational model) comfortable with their own, blissful ignorance.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  50. Re:Watcom was great. How about today? by robbyjo · · Score: 4, Interesting

    One thing I know is that their optimization routine rocks.

    Well, optimization routines can be divided into two parts: One is architecture independent (which involves simplification of AST and stuff) and the other is architecture independent. IIRC, their architecture-independent optimization was really great. It can correctly detect redundant codes and simplify it.

    I used to be an ASM programmer as I was a performance freak. When I compile my C/C++ program using Watcom, it almost always produced near optimized (i.e. the "gold-standard") asm code. I knew this when I dumped out the assembler code.

    I knew that their arch-independent optimization is really good because when you add things such as calculation of busy expression (i.e. expression that you used over and over) and stuff, it correctly cache the calculation before hand. So, you will save a tremendous time, especially if you do it in a loop. The problem was (again, IIRC) that was not perfect and some of the expressions are left undetected. But, that's probably a bug.

    IMHO, arch-independent optimization play a lot greater role than the arch-dependent one (ok, some of you may not agree with me). Things like peephole optimization is great, but is of limited usefulness once you apply the correct transformation of the AST and other internal structures.

    This is also partly why Intel optimizing compiler is also great. I heard that some of the folks are doing partial evaluation on the code -- which can greatly help speeding up the result. The idea was: If you use a particular routine (like function) only with a handful of value range, it will automatically create a specialized and optimized function for you exploiting the nature of the input values. For example: You probably have seen the routine that calculates (-1)^n used in a routine that calculates x^y. The optimizing compiler thus should be able to generate: return (n && 1 == 0) ? 1 : -1; instead of the looping. This only involves some (expensive) static analyses computations. I have yet to see this in other compilers.

    Therefore, this release is really really good thing. I hope that GNU compiler teams would pickup some of their good stuff.

    --

    --
    Error 500: Internal sig error
  51. Rise of the triad is already playable. by Anonymous Coward · · Score: 0

    Rise of the triad is already playable on Win32/Linux. And now its being ported to OpenGL.

    http://www.icculus.org/rott/

  52. Re:Hey, let's include a snide comment! by TheShadow · · Score: 1

    If every closed software publisher that opens a product gets treated like this, you won't see many more.

    Not really because no one really cares about anything micheal says anyway.

    Sometimes I wonder if he actually enjoys looking like an idiot.... hmmm....

    --

    --
    "What do you want me to do? Whack a guy? Off a guy? Whack off a guy? Cause I'm married."
  53. Ain't ya forgettin' summink? by leonbrooks · · Score: 2, Informative

    Did you Google?

    Let your fingers do the walking...

    --
    Got time? Spend some of it coding or testing
  54. Re:Watcom was great. How about today? by Ninja+Programmer · · Score: 2, Interesting
    • Or is this a scam to try to give life to a dying patient?
    No, it is not a scam. Sybase truly does not care what happens to WATCOM C/C++ (so long as it doesn't come back and bite them on the butt.)
  55. Re:Stop duplication of effort by Anonymous Coward · · Score: 0

    oh who cares gay distro like debian still compile everything optmized for a fucking 386 because there might be 1 or 2 left that arent actually floated down the fucking yangtze. so really optmizing for processor doesnt matter cuase the fucktards running the distro wont use it anyways. Even fucking people in god damn Ghana don't use fucking 386s. There is no fucking need to support the shit still. When a fucking broke ass african thinks the hardware is too shitty to use it's time to fucking stop supporting aiight??

  56. It could be used ... by Anonymous Coward · · Score: 0

    to make a Managed C++ compiler for Linux

  57. Wonderful, but... by Anonymous Coward · · Score: 1

    How many free C/C++ compilers do we need? It's nice that OS/2 has at least one free compiler suite, but who cares nowadays? Now a free, completely non-proprietary Java compiler might be nice (haven't check up on GCJ). Makes me wonder
    why Microsoft doesn't one-up Sun and release large
    portions of it's J++ product that it was supposedly planning to discontinue anyway.

  58. Re:Watcom was great. How about today? by j-pimp · · Score: 1

    GCC having competition would be very good. It would make gcc and watcom better. Auctually ReactOS might benifit from this. I'm doing the java thing and mostly database oriented stuff right now, but Its good to see stuff happening in the system programming world.

    --
    --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
  59. will all open source compilers grow together? by jdkane · · Score: 1
    and the Open Source development community to maintain and enhance the Sybase Watcom C/C++ and Fortran compiler products. -- http://www.openwatcom.org/

    So if the same open source developers work on both Watcom compilers and GNU compilers, does this mean that the best features of both will be carried back and forth (kind of unknowingly, but more out of convenience) until they start looking alike? I would assume that in the future these products may grow together, and the same destiny may apply to other open source efforts that have commonalities.

    1. Re:will all open source compilers grow together? by cimetmc · · Score: 1

      I don't think there will be much possibility to carry over stuff between Watcom and GCC for the following reasons:

      1) Carrying over source code between the 2 compilers will not be possible because both compilers are probably using completely different ways of representing the code internally during compilation.

      2) In theory, it might be possible to carry over optimization algorithms, but in practice, this may be impossible due to software patents. In fact, a lot of algorithms used in compilers are covered by software patents. GNU because of it's licensing is not allowed to use algorithms that are covered by patents. The only exception is in cases where a manufacturer grants the GNU project the right to use their patents. This has for example been the case with some pantents from IBM which are being used in GCC. Watcom OTOH contains algorithms for which Sybase has the patents and they sure don't want to share these (see their open license text). Also, they will not be able to use the patents used in GCC as they are not part of the GNU project.

      So sharing between GCC and OpenWatcom is probably mostly impossible both for technical and for legal reasons.

      Marcel

  60. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 0

    Scam? No.
    Useful? To most, probably not. To a few, possibly vital.
    For enterprise-class software, this would make me more inclined to choose SyBase since it's less likely that I'd be hung out with no possibility of support.

  61. Re:Hey, let's include a snide comment! by Anonymous Coward · · Score: 0

    It's looking like an asshole he enjoys. Looking like an idiot is just something he's good at.

  62. how open is this license really? by Anonymous Coward · · Score: 0

    it says explicitly only for personal / non-commercial use ... I don't think this could be an anlternative to GCC ...

  63. Zortech was the first with 32 bit DOS extender by Anonymous Coward · · Score: 0

    No, the Zortech compiler was the first to offer a full 32 bit DOS extender with the compiler.

  64. More like -frelease-build by yerricde · · Score: 1

    Add -fthis-program-has-no-bugs and you are done.

    So turn it off in the debug builds, but provide a way to turn it on so that you can unit-test your floating-point code both with and without -ffast-math.

    In the benchmarks that g4dget referred to, the Intel compiler was tested with the equivalent of -ffast-math turned on anyway, giving it an unfair advantage.

    --
    Will I retire or break 10K?
    1. Re:More like -frelease-build by nusuth · · Score: 1

      All dirty tricks can be used for pissing competition. Actually, on athlons, gcc 3.2.x already matches intel's compiler with C code without resorting to such tricks. For real stuff, I'd very much have correct maths and exceptions in place though.

      --

      Gentlemen, you can't fight in here, this is the War Room!

  65. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 0

    One is architecture independent [...] and the other is architecture independent.

    Wow. I wonder where they managed to fit in all the architecture dependant stuff! :)

  66. Re:Stop duplication of effort by Anonymous Coward · · Score: 0

    Did your mama teach you that language son?

  67. DJGPP & Quake by wideBlueSkies · · Score: 2, Informative

    >>The version of gcc for dos: DJGPP had a DOS extender and 32-bit support but it was slower than Watcom by a large amount

    Though that didn't stop ID software from using DJGPP to build Quake 1 way back in 96.

    --
    Huh?
  68. Re:Hey, let's include a snide comment! by NevDull · · Score: 1

    That'd be 88, dipshit. Add in the fact that you can't spell Michael, and I think you're the one looking stupid.

  69. Other Watcom trivia by Anonymous Coward · · Score: 0

    Another Watcom innovation was their 32-bit Windows extender, which I believe they brought to market even before Microsoft's Win32s. This was circa 1992, with their Watcom C/C++ 386 9.0 compiler release. This extender let you write 32-bit, flat memory model code for Windows 3.1; and layered a 32-to-16-bit thunk layer over the Win16 API.

    The developer of Watcom's 32-bit Windows extender, a University of Waterloo grad named Craig Eisler, was noticed by Microsoft and left Watcom for Microsoft around 1993. Along with Alex St. John and Eric Engstrom, Craig was the lead engineer on the first few generations of DirectX. This is described in the book, _Renegades of the Empire_ by Michael Drummond. Craig is now CEO of Action Engine, a startup in Redmond.

  70. Watcom is ok. by rice_burners_suck · · Score: 1

    I have been waiting for this day for a very long time. I have been watching the OpenWatcom project since its first days and was very excited when a LONG time after it was announced, manuals were finally available online. But still no software. Well now, it's available and I'm really happy about it. As a matter of fact, my company actually paid big bucks for this compiler back in the day. Now that the source code has been released, I'm going to modify this compiler to make highly optimized binaries out of awk scripts. When that comes to pass, humanity's purpose in the universe will have been fulfilled. Until then, I need more beer. (I only had 9 tonight...)

  71. Re:Watcom was great. How about today? by Avakado · · Score: 1

    return (n && 1 == 0) ? 1 : -1;

    This is hardly optimized. A shorter equivalent would be return -1;

    --
    The world will end in 5 minutes. Please log out.
  72. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 0

    This is hardly optimized. A shorter equivalent would be return -1;

    You probably should learn math before posting. Recall that (-1)^2 = 1.

  73. Re:Watcom was great. How about today? by Champion3 · · Score: 1

    Sybase itself was still using Watcom C++ 11.0c for SQL Anywhere Studio Windows builds until mid-2001.

    --
    I'm going to the casino. Don't gamble.
  74. Re:Watcom was great. How about today? by Anonymous Coward · · Score: 0

    I think that he was pointing out the error in the "optimized" code - using logical and instead of bitwise...

  75. Re:Watcom Memories (wrong !!) by sithlord2 · · Score: 1


    This is completely wrong !

    Watcom C/C++ 10.6 includes MFC development and still supports OS/2 and DOS (both 16bit and 32bit)

    From the Watcom 10.6 Box :

    Licensed components from :
    MS Windows 3.1 SDK
    MS Win32 SDK
    MS MFC v3.2
    MS MFC v2.52b
    IBM OS/2 2.1 toolkit
    IBM OS/2 1.3 toolkit
    IBM SOM toolkit v2.0
    Novell NLM SDK 4.0


    --
    ...You are over-qualified and under-paid. If we give you a raise, we will break the cosmic balance of the universe.
  76. Re:Watcom was great. How about today? by Matrix · · Score: 1

    Heh, there's even more than that:

    return (n && 1 == 0) ? 1 : -1;

    Let's assume this actually reads n & 1, because that's obviously what was meant (this same argument would apply for && as well):

    return (n & 1 == 0) ? 1 : -1;

    Now, "==" needs to have an equality-expression on the left hand side. & does not count as an equality-expression, so a compiler is not allowed to parse the above as

    return ( (n & 1) == 0 ) ? 1 : -1;

    1, however, does count as an equality-expression, so in fact the compiler must interpret this as:

    return ( n & (1 == 0) ) ? 1 : -1;

    which is, of course:

    return (n & 0) ? 1 : -1; ->
    return 0 ? 1 : -1; ->
    return -1;

    This can be found in ISO/IEC 9899:1999 (C99), 6.5.9 and 6.5.10.

    Of course, this isn't really important in the grand scheme of things, just thought I'd point it out... :)

    In all reality, the way the standard specifies parsing for this is wrong, logically. K&R2, page 3: "Some of the operators have the wrong precedence". Check out this posting to see why.

  77. Re:Hey, let's include a snide comment! by larry+bagina · · Score: 1

    thanks. I was hoping an expert on looking stupid could provide some useful advice.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  78. MSVC++ and templates by exp(pi*sqrt(163)) · · Score: 1

    You have to carve out a safe subset in which MSVC++ works and stick to it. You can even fake partial template specialization but it's a little ugly. (See Czarnecki's book "Generative Programming")

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  79. Re: IDE vs. compiler - get it right! by beef3k · · Score: 1

    OK, I've seen this sooooo many times now. Dev-C++ is an IDE. Yes, Integrated Development Environment, which means it integrates tools like an editor, compiler, and debugger, and possibly a GUI design tool for that toolkit or the other. Dev-C++ is no exception, and it integrates the MinGW tools like you say. There is NO SUCH THING as a "GUI compiler", it's called and IDE and it has in general nothing to do with the compiler at all. KDevelop and Dev-C++ are different IDE's, but they use the same compiler and debugger.

  80. Re:Watcom was great. How about today? by DaveHowe · · Score: 1
    I just took a look at the "open licence"

    In watford's opinion, open means "for personal use, where personal means you aren't employed by any commercial, non-commercial or government body"

    I have trouble considering this open :(

    --
    -=DaveHowe=-
  81. arch independent/dependent by Anonymous Coward · · Score: 0

    arch-independent optimization play a lot greater role than the arch-dependent one ......

    Things like peephole optimization is great but is of limited usefulness once you apply the correct transformation of the AST and other internal structures


    Arch dependent optimization is what plagues compilers in that there is no one solution to the phase ordering problem:.

    Code selection provides register allocation issues which in turn provide code selection issues which in turn provide register allocation issues which in turn...

    Oh, well, anyway, characterizing arch-dependent optimizations as simply peephole optimization opportunities seems a bit inaccurate.

  82. A typical example by exp(pi*sqrt(163)) · · Score: 1
    I can't spend all day writing sample code so here's a performance example. Apologies for the formatting. My C++ to HTML conversion script doesn't output the strict subset used by /. This implements what APL programmers call 'grade'. It sorts a bunch of integers, not by directly sorting them, but sorting their indices.

    Anyway, MSVC 6.0 compiles faster code than Intel Compiler 5.0 with /O3 optimization. If you just sort plain integers the Intel compiler is faster. But that's how it always is with people claiming their compilers are fast. Do simple examples and it works but the more complex the datastructures the slower it is. My other code that runs slower with the Intel compiler (by about 5-10%) is proprietary and includes things like fluid dynamics solvers and non-linear optimizers.

    I'll admit I have sinned in one way against Intel. I did receive a phone call from an Intel engineer while on vacation a while back asking how it was going and I should have phoned back.

    #include <windows.h>
    #include <stdio.h>
    #include <algorithm>

    //
    // This is an abuse but it's convenient and works.
    //
    ULONGLONG rdtsc() {
    _asm rdtsc;
    }

    template<class T>
    class array_lt {
    T *array;
    public:
    array_lt(T *a) : array(a) { }
    bool operator()(int a,int b) const {
    return array[a]<array[b];
    }
    };

    const int n = 10000000;
    int x[n],j[n];

    int main() {
    for (int i = 0; i<n; ++i) {
    j[i] = i;
    x[i] = i*1234567;
    }

    volatile ULONGLONG t0 = rdtsc();

    std::sort(j,j+n,array_lt<int>(x));

    volatile ULONGLONG t1 = rdtsc();

    printf(%d %d %d ... %d %d %d\n,x[j[0]],x[j[1]],x[j[2]],x[j[n-3]],x[j[n-2]],x [j[n-1]]);

    printf(%I64d MCycles\n,(t1-t0)/1000000);

    return 0;
    }

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  83. Vectorization by Aart+Bik · · Score: 1

    Since you called Intel's vectorization a "joke", I was specifically interested in examples where the Intel compiler fails to vectorize loops.
    Incidentally, your example contains one initialization loop that is nicely vectorized (so I rest my case)

    => icl sl.cpp ...
    sl.cpp(28) : (col. 1) remark: LOOP WAS VECTORIZED.

    I realize that this does not address your performance concerns (which we can discuss offline), but your example did not provide what was requested.

  84. Vectorization example by exp(pi*sqrt(163)) · · Score: 1
    int main() {
    float *x = new float[100000];

    for (int i = 0; i<100000; ++i) {
    x[i] = 0;
    }
    return 0;
    }
    . . .
    . . .
    remark: loop was not vectorized: complex pointer expression

    I thought that maybe there was some sort of variable aliasing situation going on, but the only other variables are i and x but they can happily go into registers making aliasing impossible. Am I going blind? Is there a typo in that code? Am I misisng something fundamental? Where is the 'complex pointer expression'?

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    1. Re:Vectorization example by Aart+Bik · · Score: 1

      Seriously, please try one of our latest versions! Version 7.0 has no problem with vectorizing this loop. [C:/cmplr/temp] icl /Fa /QxW sl2.cpp sl2.cpp(4) : (col. 1) remark: LOOP WAS VECTORIZED. Due to the large constant, the compiler (in combination with some alignment optimizations) is also able to see that a so-called streaming store is useful to minimize cache pollution: ... Back: movntps XMMWORD PTR [ebp+edx*4], xmm0 movntps XMMWORD PTR [ebp+edx*4+16], xmm0 add edx, 8 cmp edx, ecx jb .B1.8 ... How much speedup is actually obtained due to vectorization heavily depends on the context in which this fragment is used in your application.

    2. Re:Vectorization example by exp(pi*sqrt(163)) · · Score: 1
      Seriously, please try one of our latest versions!
      I'll try.
      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    3. Re:Vectorization example by exp(pi*sqrt(163)) · · Score: 1
      And so I tried my current project with the Intel compiler. Here are the approximate results of a typical run:

      MSVC 6.0: 115s
      IC 5.0: 145s
      IC 7.0: 140s

      These results are repeatable. The code is essentially a high dimensional optimizer with lots of sparse matrix arithmetic (sparse matrices means no vectorization of course). Classic textbook number crunching stuff. Lots of tight loops with great scope for optimization. One interesting thing: much of the code is generated by templates. Of course you can't really judge my statements unless I give you the code and that's not likely to happen. I've not tried any other projects, there's a limit to how long I can spend testing out everyone's claim to have the fastest compiler.

      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    4. Re:Vectorization example by Aart+Bik · · Score: 1

      I regret to see that again you try to change the subject by presenting the results of an application without vectorizable loops (and at the very least you could have provided some more information on the used compiler switches and target architecture). If you call someone's work a "joke", but subsequently are not willing to backup your claim due to time constraints, then I can only hope that other readers will take your claim for what it really was... If you ever have real issues with vectorization, please do not hesitate to contact me directly. Aart

    5. Re:Vectorization example by exp(pi*sqrt(163)) · · Score: 1
      Hang in a minute. I've backed up everything I've said.

      I have given an example that failed to vectorize in v5.0 (actually I remember receiving an upgrade at some point too). It was a joke. You just can't release software like that and expect me to take it seriously. It failed with the most trivial loop imaginable. (I used the default switches corresponding to selecting "fastest code possible" in the IDE and adeded /QxW and /Qvec_report4 and I'm running on a Dell Precision 530 - dual 2.2GHz Xeon CPUs (I also played with /O3 and some other options like /Qunroll)).

      I gave the performance example (same flags and architecture as above BTW) because I had two points to make: that the Intel compiler (1) has poor vectorization and (2) is lousy at optimization generally, regardless of vectorization. I made a point of saying my code didn't vectorize well so I wasn't hiding anything. I didn't want to judge your compiler unfairly on a task for which doesn't give it as much of a chance to shine as it could. I have tried to be as honest as I can. I'm sorry if this has been confusing. I have two distinct complaints.

      Going back to point (1). Yes, maybe it works in v7.0. But if some car manufacturer, say, releases a model of car that doesn't even move, would you trust them when they subsequently brought out another car that did, and that with the latter car the manufacturer produced exactly the same hype as first time? I've already paid my money for a 'vectorizing' compiler that failed to vectorize the most trivial loop. How could I be more generous? I have seen Intel compilers optimize poorly many times over the years (including now) and I have seen them vectorize poorly in the past. (He he, at one company I worked for an Intel representative actually visited my company and so we could show them there and then what the performance was like. I wish I had been at work that day.) That doesn't bode well for the future.

      And just so you don't get some funny idea about me Intel bashing (I have been known to MS bash) I'd like to declare right now that I think Intel CPUs give the best price/performance money can buy etc. And I think there are some good features in the compiler: the name mangling is compatible with MSVC++ which is valuable to me, it has excellent template support (I am very much a generic programmer) and it has clear error reporting, something else I value greatly.

      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    6. Re:Vectorization example by Aart+Bik · · Score: 1

      You may want to try adding the option -Qipo (if you have not done so already), since this can help C++ code that makes heavy use of templates (and MSVC does a -ip equivalent under -O2). If you are willing to contact me personally and provide me with some more details, I may be able to help you improve the performance of your application(s).

    7. Re:Vectorization example by exp(pi*sqrt(163)) · · Score: 1
      /Qipo made no difference at all. I just tried profile directed compilation in v7.0 for the first time ever. That did make a difference. My code went from taking 137s to 122s. But MS is produced code that runs in 114s. I'll have to try this on some other applications. Some things come in at roughly the same speed with MSVC or Intel C++ so maybe with PGO they'll end up being better than with MSVC.

      I'll have to think about getting into contact. No doubt once you have my name you'll sue me for publicly declaring my opinions :-)

      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  85. Such optimizations are not really needed by r6144 · · Score: 1
    Because no sensible programmer will write pow(-1.0,n) instead of (n&&1==0)?1:-1, especially if the code is time-critical. Programmers should never assume that the compiler can do some very specific types of optimizations, such as C tail-recursion removal, or (-1)^n stuff like this. These things can be optimized explicitly in the code, and by adding a comment describing the purpose of the code, clarity will not suffer.

    Yet certain redundent things in compiled C code are simply (nearly) impossible to optimize away. One problem is aliasing, another is the need to reload global variables after calling a function (YOU know the puts(...) doesn't change img_width, but how can the compiler know? Unless you compile the source code for puts() together with your code, and turn on inter-file optimization, a tiring thing to do). Even if an extra load cost next to nothing, and the code isn't even time critical, code size has increased considerably with no return in speed.

    So arch-independent optimizations can only do so much, and most modern compilers do this well enough, although some Intel CC features like IPO are also desirable. Arch-dependent things seem to be more important currently, and they are also the things that need constant development now, to keep pace with the introduction of new CPU generations.