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 1/9] ENABLE_CHECKING refactoring

On 10/21/2015 10:18 AM, Richard Biener wrote:

On October 21, 2015 6:04:38 PM GMT+02:00, Bernd Schmidt <bschmidt@redhat.com> wrote:

On 10/21/2015 05:56 PM, Jeff Law wrote:

The problem is the existing ENABLE_CHECKING conditions.

Anything which is #ifdef ENABLE_CHECKING will have its behavior

changed

if we change things so that ENABLE_CHECKING is always defined with a

value.


So if we wanted to continue to use ENABLE_CHECKING, but with a value,
then every #ifdef has to be fixed all-at-once.


But why change it to have a value? Just keep it as-is, and use
flag_checking for runtime tests.


The goal is to get rid of conditional compilation.
Precisely. I've been watching some other projects going down this path and seeing good results. I strongly believe it'll help drive down the development/maintenance costs for GCC.
I might even claim it's already helping. While we're still seeing syntax errors in the conditionally compiled code, it doesn't feel like we're seeing it as often as in the past. That's purely anecdotal based on what I've seen fly by over the last couple years. 


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