This is the mail archive of the gcc@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]

Re: bug 2645 and restrict

Mark Mitchell <mark@codesourcery.com> writes:

| >>>>> "Jason" == Jason Merrill <jason_merrill@redhat.com> writes:
| 
| >>>>> "Gabriel" == Gabriel Dos Reis <gdr@codesourcery.com> writes:
| 
|     >> I don't agree. The description given by Nathan applies as well
|     >> to volatile.
| 
|     Jason> I agree with Fergus that this is unfortunate.  But I
|     Jason> suppose I'd be happy to accept __restrict__ in this
|     Jason> situation with a warning.
| 
| Yes, that makes sense to me too.  (Same goes for volatile, actually.)
| If we're ignoring the qualifier, issue a plain warning; a pedwarn is
| too strong because that will halt compilation.

I'm convinced.

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]