Re: Adding Blank Line In Source Causes Change In Executable

HOKIENERD <hokienerd@gmail.com>
Mon, 26 Mar 2012 07:33:29 -0700 (PDT)

          From comp.compilers
Related articles
Adding Blank Line In Source Causes Change In Executable john.m.morris@navy.mil (Morris, John M CIV NSWCDD, Q34) (2012-03-06)
Re: Adding Blank Line In Source Causes Change In Executable gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-03-06)
Re: Adding Blank Line In Source Causes Change In Executable bobduff@shell01.TheWorld.com (Robert A Duff) (2012-03-06)
Re: Adding Blank Line In Source Causes Change In Executable hokienerd@gmail.com (HOKIENERD) (2012-03-12)
Re: Adding Blank Line In Source Causes Change In Executable bobduff@shell01.TheWorld.com (Robert A Duff) (2012-03-13)
Re: Adding Blank Line In Source Causes Change In Executable gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-03-14)
Re: Adding Blank Line In Source Causes Change In Executable hokienerd@gmail.com (HOKIENERD) (2012-03-26)
Re: Adding Blank Line In Source Causes Change In Executable bobduff@shell01.TheWorld.com (Robert A Duff) (2012-03-26)
| List of all articles for this month |
From: HOKIENERD <hokienerd@gmail.com>
Newsgroups: comp.compilers
Date: Mon, 26 Mar 2012 07:33:29 -0700 (PDT)
Organization: Compilers Central
References: 12-03-007 12-03-010 12-03-028 12-03-031
Keywords: code, debug
Posted-Date: 26 Mar 2012 10:59:03 EDT

I finally got to the assembly code, and it is indeed rcheck_12 (and a
few similar checks).


We were hoping to add comments throughout the code, and 'prove' that
they had no effect by producing an identical executable, but it looks
like we won't be able to do that.


The line number is useful in our debug environment, but in our final
system there is nowhere for the information to be output, so it won't
do us any good in that configuration.


I sure can't find a way to turn it off on my system!


Thanks for all the help!


John

Post a followup to this message

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