| Subject: | Re: Strange bit shifting result with gcc - am I missing something obvious? |
|---|---|
| From: | |
| Date: | Sun, 30 Mar 2008 19:37:03 -0400 |
| Newsgroups: | comp.lang.c |
Boltar <boltar2003@xxxxxxxxxxx> wrote: > > It isn't? Thats bloody annoying since that means i'll have to do a > specific check for the bit shift count being > than the size of the > type being shifted. The theory is it's better to have to have an explicit check for the relatively small amount of code that needs it than to have the compiler always generate for the vast majority of code that doesn't need it. -Larry Jones OK, what's the NEXT amendment say? I know it's in here someplace. -- Calvin |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ?: as an lvalue, Andrey Tarasevich |
|---|---|
| Next by Date: | Re: Strange bit shifting result with gcc - am I missing something obvious?, lawrence . jones |
| Previous by Thread: | Re: Strange bit shifting result with gcc - am I missing something obvious?, Eric Sosman |
| Next by Thread: | Re: Strange bit shifting result with gcc - am I missing something obvious?, Keith Thompson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |