[Bug target/40697] inefficient code to extract least bits from an integer value

2010-03-20 Thread ramana at gcc dot gnu dot org
--- Comment #6 from ramana at gcc dot gnu dot org 2010-03-20 19:32 --- Now Fixed . Yay. -- ramana at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/40697] inefficient code to extract least bits from an integer value

2010-03-19 Thread bernds at gcc dot gnu dot org
--- Comment #5 from bernds at gcc dot gnu dot org 2010-03-19 18:41 --- Subject: Bug 40697 Author: bernds Date: Fri Mar 19 18:41:22 2010 New Revision: 157582 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=157582 Log: gcc/ PR target/40697 * optabs.c

[Bug target/40697] inefficient code to extract least bits from an integer value

2010-03-16 Thread bernds at codesourcery dot com
--- Comment #4 from bernds at codesourcery dot com 2010-03-16 10:56 --- Created an attachment (id=20117) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20117action=view) A patch to fix it. The andsi3 expander has code to do the right thing, but avoid_expensive_constant prevents it

[Bug target/40697] inefficient code to extract least bits from an integer value

2009-07-09 Thread carrot at google dot com
--- Comment #1 from carrot at google dot com 2009-07-09 09:24 --- Created an attachment (id=18166) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18166action=view) test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40697

[Bug target/40697] inefficient code to extract least bits from an integer value

2009-07-09 Thread steven at gcc dot gnu dot org
--- Comment #2 from steven at gcc dot gnu dot org 2009-07-09 09:59 --- Maybe we can fix this in expand instead: if we see (x CONST) and CONST is a masking constant that isn't a legitimate constant for the the target, then see if the sum of the rtx_cost of expressing the mask as shifts

[Bug target/40697] inefficient code to extract least bits from an integer value

2009-07-09 Thread ramana at gcc dot gnu dot org
--- Comment #3 from ramana at gcc dot gnu dot org 2009-07-09 10:32 --- (In reply to comment #2) Maybe we can fix this in expand instead: if we see (x CONST) and CONST is a masking constant that isn't a legitimate constant for the the target, then see if the sum of the rtx_cost of