public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/48783] ~0ULL % (a / (a & -a)) == 0 is not optimized to false on the tree level Date: Sun, 29 Jan 2012 04:51:00 -0000 [thread overview] Message-ID: <bug-48783-4-GrOdAZdNPL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48783-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48783 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization, TREE Target|Arm | Last reconfirmed|2011-05-31 22:28:11 |2012-01-28 Component|c |tree-optimization Summary|ARM: kernel compiled at -O2 |~0ULL % (a / (a & -a)) == 0 |has a unused reference to |is not optimized to false |__aeabi_uldivmod |on the tree level --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-29 01:44:28 UTC --- ~0ULL % (a / (a & -a)) == 0 Is not optimized to false on the tree level. Basically we should figure that out and we would then remove the reference to the uldivmod libcall.
next prev parent reply other threads:[~2012-01-29 1:45 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-26 23:46 [Bug c/48783] New: ARM: kernel compiled at -O2 has a unused reference to __aeabi_uldivmod michael.hope at linaro dot org 2011-04-27 9:43 ` [Bug c/48783] " ams at gcc dot gnu.org 2011-04-27 9:56 ` michael.hope at linaro dot org 2011-04-27 10:13 ` michael.hope at linaro dot org 2011-04-27 11:09 ` ams at gcc dot gnu.org 2011-05-31 22:31 ` ramana at gcc dot gnu.org 2012-01-29 4:51 ` pinskia at gcc dot gnu.org [this message] 2023-01-30 18:40 ` [Bug tree-optimization/48783] ~0ULL % (a / (a & -a)) == 0 is not optimized to false on the tree level pinskia at gcc dot gnu.org 2023-01-30 18:43 ` pinskia at gcc dot gnu.org 2023-08-18 13:57 ` jemarch at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-48783-4-GrOdAZdNPL@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).