If I use the /Gy options, the warning go away for all projects but one. I will admit that there are a few functions that could be break down in smaller functions.
My question is: Is there a potential problem on the GCPlus if I ignore that warning? Can I ignored the warning if everything was working fine when compiled with eVc 3.0?
The problem is specific to method code spanning pages on the OMAPs. If you're certain that the binary you're building will never be run on a TI processor you can safely ignore the warning. If there's a possibility that you may run the binary on a TI processor, or to simply avoid the possible risk of the bug from processors that haven't been released, you might consider splitting the large functions into smaller code blocks.