Re: A trick question

On Apr 21, 1:35 am, Keith Thompson <ks...@xxxxxxx> wrote:

Thanks for the corrections!


Thanks everyone for a very interesting discussion. Since I have this
compiler and it generates an assembly pass as its primary pass, I
could have provided the assembly for review as well and we could have
added code to diagnose this at that level. But I think you are just
having fun with this or you probably would have asked someone to do so.
.

Relevant Pages

  • Re: The annotated annotated annotated C standard
    ... But you don't need to be clever to write a broken compiler. ... What "Feather did to Schildt" was review his book. ... written a working compiler for your book, well, I still find that hard to ...
    (comp.programming)
  • RE: Micro$oft warns of undetectable spyware security risk ...
    ... Contrast this with a closed compiler ... The number of open source advocates who understand driver/kernel/os ... interest (remember they are likely not being paid to review all this ... bank building and vault available to everyone is going to make the bank ...
    (comp.os.vms)
  • Re: panic error
    ... Whoever put that message in a C compiler was just being silly. ... Error: There is something badly wrong with the installation directory: ... But hey, "Panic:" is just oh so much more fun, and a sure sign that the ... that one that outputs error messages, the ONLy thing to do is just ...
    (comp.lang.c)
  • Re: GFORTRAN PROBLEM WITH SAVE STATEMENT
    ... module end pulls error. ... specification statement. ... If you ever had a compiler that failed to diagnose this, ...
    (comp.lang.fortran)
  • Re: c_loc - error with gfortran, not ifort
    ... While this method has some advantages, a disadvantage is that there is nothing the compiler can "hook into" to diagnose such errors of usage. ... User communities for Intel Software Development Products ...
    (comp.lang.fortran)