public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35466] Different assembly codes on 32bit and 64bit hosts
Date: Thu, 06 Mar 2008 13:39:00 -0000 [thread overview]
Message-ID: <20080306133855.30600.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35466-682@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rguenth at gcc dot gnu dot org 2008-03-06 13:38 -------
32bit HWI cannot represent 128bit constants. If you are lucky and it works as
far as creating code you should not be surprised that some constants might
be forced to memory. The only chance to generate the same code in this context
is to pessimize code generation for 64bit HWI. We are not going to do that.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35466
next prev parent reply other threads:[~2008-03-06 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 4:13 [Bug target/35466] New: " hjl dot tools at gmail dot com
2008-03-05 4:28 ` [Bug target/35466] " hjl dot tools at gmail dot com
2008-03-05 7:40 ` steven at gcc dot gnu dot org
2008-03-05 7:50 ` pinskia at gcc dot gnu dot org
2008-03-06 9:44 ` rguenth at gcc dot gnu dot org
2008-03-06 13:33 ` jsm28 at gcc dot gnu dot org
2008-03-06 13:39 ` rguenth at gcc dot gnu dot org [this message]
2008-03-06 13:52 ` jsm28 at gcc dot gnu dot org
2009-04-07 16:52 ` info dot gnu at rt-labs dot com
2009-04-08 6:07 ` hp at gcc dot gnu dot org
2009-09-17 9:41 ` ubizjak at gmail dot com
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=20080306133855.30600.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).