http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45511
--- Comment #7 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-06-16 23:15:47 UTC --- On Thu, 16 Jun 2011, rmansfield at qnx dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45511 > > --- Comment #6 from Ryan Mansfield <rmansfield at qnx dot com> 2011-06-16 > 23:00:25 UTC --- > (In reply to comment #5) > > EABI targets force 64-bit HOST_WIDE_INT, so the vast majority of users of > > the ARM port won't hit this assert. If you really care about old-ABI > > targets (and deprecation of arm-linux-gnu and arm-elf is long overdue), > > maybe ARM should just force 64-bit HOST_WIDE_INT unconditionally. > > Thanks for replying, JSM. Looking at config.gcc, there still seems to be a > quite a number of targets that still use the apcs-gnu ABI. Are you suggesting > all of the non-EABI targets be deprecated, or just the arm-linux-gnu/arm-elf > configurations? Is there any downside or reason why not to add > need_64bit_hwint=yes for all arm targets? The suggested deprecation is of arm-linux-gnu, obsoleted by arm-linux-gnueabi, arm-elf, obsoleted by arm-eabi, and probably arm-uclinux, obsoleted by arm-uclinuxeabi. It's been suggested that 64-bit HOST_WIDE_INT compilers are slower on 32-bit hosts than those with 32-bit HOST_WIDE_INT, but I haven't seen any figures, and think in practice it would be better to use 64-bit HOST_WIDE_INT unconditionally for *all* hosts and targets and so eliminate one source of host-dependency bugs.
