[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-28 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 Thomas Koenig changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-23 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 --- Comment #4 from Janne Blomqvist --- Actually, I think it's for big endian we could optimize memcmp_char4. In the example Thomas posted on the mailing list, one must also check the sign of memcmp, not just whether it's != 0. Fixed example:

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 Janne Blomqvist changed: What|Removed |Added CC||jb at gcc dot gnu.org --- Comment #3

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-22 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 --- Comment #2 from Janne Blomqvist --- Author: jb Date: Wed Nov 22 19:19:13 2017 New Revision: 255072 URL: https://gcc.gnu.org/viewcvs?rev=255072=gcc=rev Log: PR 83097 Use __BYTE_ORDER__ predefined macro instead of runtime check By using the

[Bug libfortran/83097] Use __BYTE_ORDER__ instead of runtime test

2017-11-22 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83097 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|