search for: rezext

...n i32 here intentionally. This prompts me to the following thought, which may not be helpful. Perhaps we might introduce something like the following two pseudo-instructions in the IR: resext sign extend on a quantity that the front end asserts has already been sign extended. rezext zero extend on a quantity that the front end asserts has already been zero extended. These instructions serve to advise the caller-side optimizer that the required extend has been done, which tells us what we need to know for optimizations. If they inadvertently make it to the back e...

...s prompts me to the following thought, which may not be helpful. > Perhaps we might introduce something like the following two > pseudo-instructions in the IR: > > resext sign extend on a quantity that the front end asserts has > already been sign extended. > > rezext zero extend on a quantity that the front end asserts has > already been zero extended. > > These instructions serve to advise the caller-side optimizer that the > required extend has been done, which tells us what we need to know for > optimizations. If they inadvertentl...

On May 16, 2008, at 11:12 AM, <Alireza.Moshtaghi at microchip.com> <Alireza.Moshtaghi at microchip.com > wrote: > > Chris, > I did not quite understand the “The bad thing about …” part of your > argument. I’m not sure which of the two scenarios are you comparing > (promoting in FrontEnd vs BackEnd) or (promotion to int vs i32) Assume we make the change I

Chris, I did not quite understand the "The bad thing about ..." part of your argument. I'm not sure which of the two scenarios are you comparing (promoting in FrontEnd vs BackEnd) or (promotion to int vs i32) Regardless, I agree with you and shap that promotions should take place in the FrontEnd and this is my reason: The standard allows calling a function without prototype and