This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/65668] gcc does not know how to use __eabi_uldivmod properly
- From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 27 Aug 2016 12:14:22 +0000
- Subject: [Bug middle-end/65668] gcc does not know how to use __eabi_uldivmod properly
- Auto-submitted: auto-generated
- References: <bug-65668-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65668
prathamesh3492 at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |prathamesh3492 at gcc dot gnu.org
--- Comment #3 from prathamesh3492 at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #1)
> There was a few patches for __eabi_uldivmod improvement floating around I
> don't know what happened to them.
Hi,
The divmod patch is blocked by an issue with optab_libfunc(sdivmod_optab,
DImode) returning bogus libfunc "__divmoddi4", instead of NULL_RTX.
I had asked for suggestions to work around the issue here:
https://gcc.gnu.org/ml/gcc/2016-08/msg00120.html
Alternatively the patch could drop targeting generic divmod libfunc
(the only one available is __udivmoddi4) and only perform the optimization
if target-specific divmod libfunc is available, which bypasses the
optab_libfunc issue.
Posted patch for that here:
https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01069.html
I am not sure which of the two approaches is more reasonable
and would be grateful for suggestions.
Thanks,
Prathamesh