X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: pavenis AT lanet DOT lv
To: Manuel Collado <m DOT collado AT aaron DOT ls DOT fi DOT upm DOT es>, djgpp AT delorie DOT com
Date: Tue, 30 Apr 2002 13:18:02 +0300
MIME-Version: 1.0
Subject: Re: gcov for gcc-3.0.x fails if not LFN support
Message-ID: <3CCE998A.826.734BF7@localhost>
In-reply-to: <3CCD93EE.1CFCEB45@lml.ls.fi.upm.es>
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 29 Apr 2002 at 20:41, Manuel Collado wrote:

> I think I've found a small bug on DJGPP ports of gcov in gcc-3.0.3 and
> gcc-3.0.4. According to the gcc README file, this newgroup is the place
> for reporting DJGPP port bugs. If not, please let me know and point me
> in the right direction.
> 
> The problem is that gcov is not able to create the output file for a
> 'name.ext' source file if LFN is not available. The generated name is
> 'name.ext.gcov', that breaks the 8+3 rule.
> 
> This problem don't arise in gcc-2.95.3. Looking at the sources, I see a
> small code fragment for special handling of the output file name in
> absence of LFN support that is present in 2.95.3 but not in 3.0.3 nor in
> 3.0.4 versions of gcc.
> 
> The problem shows up in my Windows NT 4.0 worksation system, but I
> suppose it affect also any system with no LFN support. The easiest
> workarount is to keep gcov.exe from gcc-2.95.3.

Patch was somehow left out of my patchset for gcc-3.0.X. 
Put it back there now, but I don't know whether I build gcc-3.0.X any more.
Put it also in patchset for upcoming gcc-3.1 (gcc-3.1 is not released yet)

Andris