public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/41526] gimple bytecode streams are not portable between different hosts
Date: Mon, 04 Jul 2022 09:03:29 +0000 [thread overview]
Message-ID: <bug-41526-4-0IeTho3sed@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41526-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41526
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2010-09-01 19:29:58 |2022-7-4
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #9)
> *** Bug 106177 has been marked as a duplicate of this bug. ***
The float encoding issue was re-confirmed here.
I'm not sure if we meanwhile have a per-file LTO header but it might be
nice to put enough info there to give a reasonable error. As said
endianess is a hard issue to fix, likewise int/long/pointer size differences.
The float encoding part could be fixed in theory.
target specific issues with host dependences might also exist (host
dependent flags might be streamed?).
Regression testing is another obvious problem here.
next prev parent reply other threads:[~2022-07-04 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41526-4@http.gcc.gnu.org/bugzilla/>
2021-12-26 2:07 ` pinskia at gcc dot gnu.org
2022-05-18 12:43 ` rguenth at gcc dot gnu.org
2022-07-04 8:41 ` rguenth at gcc dot gnu.org
2022-07-04 9:03 ` rguenth at gcc dot gnu.org [this message]
2022-07-04 9:28 ` richard at weickelt dot de
2009-09-30 19:37 [Bug lto/41526] New: " dnovillo at gcc dot gnu dot org
2009-09-30 19:50 ` [Bug lto/41526] " dnovillo at gcc dot gnu dot org
2009-09-30 20:17 ` dnovillo at gcc dot gnu dot org
2010-09-01 19:30 ` jsm28 at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-41526-4-0IeTho3sed@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).