public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/41565] -m32 causes an ICE when the object files were compiled with 64bit
Date: Sun, 04 Oct 2009 12:17:00 -0000 [thread overview]
Message-ID: <20091004121710.19727.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41565-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from joseph at codesourcery dot com 2009-10-04 12:17 -------
Subject: Re: New: -m32 causes an ICE when the object files
were compiled with 64bit
While this case should give a sensible error (not an ICE), linking an
object built with a 32-bit compiler with no special options and one built
with a 64-bit compile with -m32 should work with LTO if it would work
without [*]. So if we cause an error in that case, we should make sure
there's a PR for fixing it.
[*] This depends on bug 41526 being fixed if the *hosts* differ in
HOST_BITS_PER_WIDE_INT or HOST_BITS_PER_LONG settings.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41565
next prev parent reply other threads:[~2009-10-04 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 6:41 [Bug lto/41565] New: " pinskia at gcc dot gnu dot org
2009-10-04 9:25 ` [Bug lto/41565] " rguenth at gcc dot gnu dot org
2009-10-04 9:54 ` rguenth at gcc dot gnu dot org
2009-10-04 9:58 ` rguenth at gcc dot gnu dot org
2009-10-04 12:17 ` joseph at codesourcery dot com [this message]
2009-10-05 9:49 ` rguenth at gcc dot gnu dot org
2009-10-08 23:06 ` pinskia at gcc dot gnu dot org
2009-10-08 23:08 ` pinskia at gcc dot gnu dot org
2009-10-13 12:42 ` rguenth at gcc dot gnu dot org
2009-10-13 12:43 ` rguenth at gcc dot gnu dot org
2009-10-13 22:36 ` pinskia at gcc dot gnu dot org
2009-10-13 22:41 ` pinskia 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=20091004121710.19727.qmail@sourceware.org \
--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).