From: Geoff Keating <geoffk@geoffk.org>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: rfc: constant pool and floats
Date: Sun, 17 Oct 2004 02:41:00 -0000 [thread overview]
Message-ID: <20B4F160-1FB9-11D9-A03C-000A95B1F520@geoffk.org> (raw)
In-Reply-To: <20041016023058.GA9787@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
On 15/10/2004, at 7:30 PM, Aldy Hernandez wrote:
>> That's the problem. Clearly, (reg:SF 120) is not equal to the
>> CONST_INT; it's equal to a SFmode CONST_DOUBLE.
>
> I played around kludging the REG_EQUAL to be equal to a CONST_DOUBLE.
> That didn't fix the problem because when we fill in the constant pool
> (force_const_mem) with the value, we fill it in with a const_int/SFmode
> pair, which still causes the abort while dumping the constant pool.
Where did the CONST_INT come from, if not the REG_EQUAL note?
> /* If VALUE is a floating-point mode, access it as an integer of the
> corresponding size. This can occur on a machine with 64 bit
> registers
> that uses SFmode for float. This can also occur for unaligned
> float
> structure fields. */
> if (GET_MODE_CLASS (GET_MODE (value)) != MODE_INT
> && GET_MODE_CLASS (GET_MODE (value)) != MODE_PARTIAL_INT)
> value = gen_lowpart ((GET_MODE (value) == VOIDmode
> ? word_mode : int_mode_for_mode (GET_MODE (value))),
> value);
This code is not wrong, as such, but I'm a bit confused about what then
happens to 'value'. The routine appears to return it, but there's no
documentation about what the routine is *supposed* to return, and every
use of it in the compiler appears to ignore the return value.
Anyway, what you want to look for is the first point where SFmode and
CONST_INT get associated with each other.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2410 bytes --]
next prev parent reply other threads:[~2004-10-16 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 21:45 Aldy Hernandez
2004-10-15 23:04 ` Andrew Pinski
2004-10-16 1:07 ` Daniel Jacobowitz
2004-10-16 10:41 ` Aldy Hernandez
2004-10-16 2:31 ` Aldy Hernandez
2004-10-15 23:57 ` Geoffrey Keating
2004-10-16 9:19 ` Aldy Hernandez
2004-10-17 2:41 ` Geoff Keating [this message]
2004-10-17 15:40 ` Aldy Hernandez
2004-10-17 16:13 ` David Edelsohn
2004-10-17 16:58 ` Geoff Keating
2004-10-18 22:59 ` Aldy Hernandez
2004-10-19 4:04 ` Aldy Hernandez
2004-10-19 22:13 ` Aldy Hernandez
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=20B4F160-1FB9-11D9-A03C-000A95B1F520@geoffk.org \
--to=geoffk@geoffk.org \
--cc=aldyh@redhat.com \
--cc=gcc@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).