diff options
| author | landley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2006-09-15 04:08:25 +0000 |
|---|---|---|
| committer | landley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2006-09-15 04:08:25 +0000 |
| commit | 68ba5834bc9c90719ab6cfb4d4916eb05f8fedd9 (patch) | |
| tree | 3900da8babd792ef2205fa2dd56b65fc2c1eb03e /shell | |
| parent | 962447c29b16ac6aa4abaafc29d39755543de72f (diff) | |
| download | busybox-w32-68ba5834bc9c90719ab6cfb4d4916eb05f8fedd9.tar.gz busybox-w32-68ba5834bc9c90719ab6cfb4d4916eb05f8fedd9.tar.bz2 busybox-w32-68ba5834bc9c90719ab6cfb4d4916eb05f8fedd9.zip | |
So, in the cornucopia of superfulous warning directives I didn't add to the
tree, we have the warning about failed inlines (which with our inline
limit set to zero means any usage of the "inline" keyword at all). Note
that setting the inline limit to zero, and using -Werror, both predated
adding the warning about inlines to the tree. So whatever checkin added
that did nothing but break the tree. But oh well.
The second category of superfluous warnings is warning about functions with
no previous declaration. Apparently, if you add ALWAYS_INLINE to an empty
function definition, it considers the sucker undeclared as far as the
warning is concerned. (I.E. it's a buggy warning. I try not to ask the
compiler to generate warnings it can't competently generate.)
This is why I removed "inline" (unbreak allbareconfig), and couldn't replace it
with "ALWAYS_INLINE" (still broke allbareconfig).
git-svn-id: svn://busybox.net/trunk/busybox@16126 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'shell')
0 files changed, 0 insertions, 0 deletions