Re: GCOV
Hello John,
for the .re ones i could simply release re2c 0.9.10 and you use the new
switch we especially made for that. If i knew we were going for 5.1 i had
probably done that at OSCON but i didn't see any action required until just
now.
best regards
marcus
Tuesday, August 9, 2005, 10:44:01 PM, you wrote:
> I also wrote one, i don't care which we use... it's a 5 line shell
> script :)
> On Tue, 2005-08-09 at 16:40 -0400, Wez Furlong wrote:
>> IIRC, we have a script that does this already for our release
>> tarballs; should save some effort.
>>
>> --Wez.
>>
>> On 8/9/05, John Coggeshall <john@coggeshall.org> wrote:
>> > Before we deep-freeze the CVS, I'd like to get my GCOV stuff committed.
>> > The changes are relatively minor and I've already run it past Andi. I'm
>> > trying to get around one last problem that maybe someone else can take
>> > care of:
>> >
>> > The basic issue is that our parsers have broken file/line preprocessor
>> > directives... since we're pre-generating these files and then committing
>> > them, things like #file and #line are breaking gcov because it's using
>> > them to look for source and the paths are from whomever committed them
>> > to begin with. I spoke with Andi about this at OSCON and we agreed that
>> > it's probably best when GCOV is enabled to strip those preprocessor
>> > directives out beforehand. Any other thoughts/comments? If no one has a
>> > better solution I'll commit the code later today.
Thread (12 messages)