[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2022-07-04 Thread richard at weickelt dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 --- Comment #11 from Richard Weickelt --- I would prefer a warning over an error. Cross-compiling for arm-none-eabi does work unless floating point arithmetic is involved as reported in bug 105641, but I understand that this might be a special

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2022-07-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 Richard Biener changed: What|Removed |Added Last reconfirmed|2010-09-01 19:29:58 |2022-7-4 --- Comment #10 from Richard

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2022-07-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 Richard Biener changed: What|Removed |Added CC||clyon at gcc dot gnu.org --- Comment

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2022-05-18 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 Richard Biener changed: What|Removed |Added CC||richard at weickelt dot de --- Comment

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2021-12-25 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 Andrew Pinski changed: What|Removed |Added CC||daniel.f.starke at freenet dot de ---

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2019-10-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 Richard Biener changed: What|Removed |Added Keywords||lto --- Comment #6 from Richard Biener

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2019-10-28 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 --- Comment #5 from joseph at codesourcery dot com --- My previous comment was that the *patch* for that old bug was a host-dependency, so the bug having been closed as fixed suggests that the issue may be present in the source tree, not that

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2019-10-27 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526 --- Comment #4 from Eric Gallager --- (In reply to Joseph S. Myers from comment #3) > The handling of target options (the patch for bug 45475) is another > host-dependency in the bytecode stream. That has been closed as fixed... which parts of

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2010-09-01 Thread jsm28 at gcc dot gnu dot org
--- Comment #3 from jsm28 at gcc dot gnu dot org 2010-09-01 19:29 --- The handling of target options (the patch for bug 45475) is another host-dependency in the bytecode stream. -- jsm28 at gcc dot gnu dot org changed: What|Removed |Added

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2009-09-30 Thread dnovillo at gcc dot gnu dot org
--- Comment #1 from dnovillo at gcc dot gnu dot org 2009-09-30 19:50 --- Other portability concerns: http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02157.html The host portability issue with __attribute__ ((visibility (hidden))) has already been noted. I suggest conditioning the

[Bug lto/41526] gimple bytecode streams are not portable between different hosts

2009-09-30 Thread dnovillo at gcc dot gnu dot org
--- Comment #2 from dnovillo at gcc dot gnu dot org 2009-09-30 20:17 --- More portability concerns from http://gcc.gnu.org/ml/gcc-patches/2009-09/msg02157.html +/* This needs to be included after config.h. Otherwise, _GNU_SOURCE will not + be defined in time to set __USE_GNU in