This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Don't error on coverage mismatch by request

From: Jan Hubicka <hubicka at ucw dot cz>
To: Jan Hubicka <hubicka at ucw dot cz>
Cc: Richard Guenther <richard dot guenther at gmail dot com>, Richard Guenther <rguenther at suse dot de>, gcc-patches at gcc dot gnu dot org, Jan Hubicka <jh at suse dot cz>
Date: Sun, 14 Jan 2007 19:13:11 +0100
Subject: Re: [PATCH] Don't error on coverage mismatch by request
References: <Pine.LNX.4.64.0611291340220.30849@zhemvz.fhfr.qr> <84fc9c000701140941y3b9c4eb9t16fdb2fe0d900168@mail.gmail.com> <20070114174625.GE3959@atrey.karlin.mff.cuni.cz> <84fc9c000701140950o40f711c2g8e9adea150ef47fa@mail.gmail.com> <20070114181031.GF3959@atrey.karlin.mff.cuni.cz>

Hi,
just to add, I definitly see that option is useful when you know you
changed someting not important.  Just in the past, when mismatches was
warnings by default, I got number of false bugreports complaining about
code quality being poor with profile feedback that has turned out to be
mishandled profile. So I would preffer the compiler to be a bit
educational by default ;)

Honza

References:
- Re: [PATCH] Don't error on coverage mismatch by request
  - From: Richard Guenther
- Re: [PATCH] Don't error on coverage mismatch by request
  - From: Jan Hubicka
- Re: [PATCH] Don't error on coverage mismatch by request
  - From: Richard Guenther
- Re: [PATCH] Don't error on coverage mismatch by request
  - From: Jan Hubicka

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]