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: assertify mn10300


Alexandre Oliva <aoliva@redhat.com> writes:

> On May  7, 2005, Zack Weinberg <zack@codesourcery.com> wrote:
>> and a compromise was reached (--enable-checking=release doesn't
>> disable gcc_assert, you have to build specifically with
>> --disable-checking).
>
> I see.  I was misled by a recent patch I posted, in which Roger Sayle
> recommended me not to use gcc_assert in a certain case because it
> would remove the desired side effects should checking be disabled.  I
> didn't realize releases no longer had all forms of checking disabled.

I don't recall exactly what Roger said, but I think he was commenting
on a case where the side-effect should always be executed, even when
the data structure is correct.

> That was not my intention.  Sorry if it sounded like that.

No worries.

zw


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