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: GCC loop iterations and wrapping

From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
To: GCC Patches <gcc-patches at gcc dot gnu dot org>, Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>, sebastian dot pop at cri dot ensmp dot fr
Date: Sun, 23 Oct 2005 14:48:54 +0200
Subject: Re: GCC loop iterations and wrapping
References: <200510171439.j9HEdRq29556@makai.watson.ibm.com> <20051017161246.GA5937@napoca.cri.ensmp.fr> <200510171705.j9HH53q28188@makai.watson.ibm.com> <20051017182521.GA929@napoca.cri.ensmp.fr> <200510171833.j9HIXvq39648@makai.watson.ibm.com> <20051017185146.GA19710@napoca.cri.ensmp.fr> <200510181925.j9IJPtq27920@makai.watson.ibm.com> <20051021172109.GA31610@napoca.cri.ensmp.fr> <20051021180623.GA13448@atrey.karlin.mff.cuni.cz> <20051021181953.GA348@napoca.cri.ensmp.fr> <20051022212120.GA8849@atrey.karlin.mff.cuni.cz>

I would prefer having the check whether the conversion is valid
split to a separate function, so that it can be used without code
duplication; something like the following patch, bootstrapped &
regtested on ia64.

It would be good if the check triggered a warning for -Wunsafe-loop-optimizations.

A possible design is to add a bool unsafe_opt to struct loop, and set it to avoid duplicated warning.

Paolo

References:
- Re: GCC loop iterations and wrapping
  - From: Sebastian Pop
- Re: GCC loop iterations and wrapping
  - From: Zdenek Dvorak
- Re: GCC loop iterations and wrapping
  - From: Sebastian Pop
- Re: GCC loop iterations and wrapping
  - From: Zdenek Dvorak

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