[Bug c/60490] New: please define __LITTLE_ENDIAN__/__BIG_ENDIAN__ for every target where it makes sense

["rafael.espindola at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60490

            Bug ID: 60490
           Summary: please define __LITTLE_ENDIAN__/__BIG_ENDIAN__ for
                    every target where it makes sense
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rafael.espindola at gmail dot com
                CC: chandlerc at gmail dot com, echristo at gmail dot com

We noticed that both clang and gcc were fairly inconsistent and incompatible as
to which targets cause __LITTLE_ENDIAN__/__BIG_ENDIAN__ to be defined.

They are not as flexible __BYTE_ORDER__ (cannot represent
__ORDER_PDP_ENDIAN__), but they cover the needs of most software. On the clang
side we decided to just always define them if the target is little endian or
big endian.

It would be nice if gcc could do the same.