summaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/iwlwifi
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2009-03-17 10:02:35 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2009-03-17 10:02:35 -0700
commitee568b25ee9e160b32d1aef73d8b2ee9c05d34db (patch)
treea29f070d82e6f787570213161c4c46c16ca6ef8a /drivers/net/wireless/iwlwifi
parent30390880debce4a68fd23e87a787f27609e4bf4a (diff)
downloadblackbird-op-linux-ee568b25ee9e160b32d1aef73d8b2ee9c05d34db.tar.gz
blackbird-op-linux-ee568b25ee9e160b32d1aef73d8b2ee9c05d34db.zip
Avoid 64-bit "switch()" statements on 32-bit architectures
Commit ee6f779b9e0851e2f7da292a9f58e0095edf615a ("filp->f_pos not correctly updated in proc_task_readdir") changed the proc code to use filp->f_pos directly, rather than through a temporary variable. In the process, that caused the operations to be done on the full 64 bits, even though the offset is never that big. That's all fine and dandy per se, but for some unfathomable reason gcc generates absolutely horrid code when using 64-bit values in switch() statements. To the point of actually calling out to gcc helper functions like __cmpdi2 rather than just doing the trivial comparisons directly the way gcc does for normal compares. At which point we get link failures, because we really don't want to support that kind of crazy code. Fix this by just casting the f_pos value to "unsigned long", which is plenty big enough for /proc, and avoids the gcc code generation issue. Reported-by: Alexey Dobriyan <adobriyan@gmail.com> Cc: Zhang Le <r0bertz@gentoo.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/net/wireless/iwlwifi')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud