public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49798] .quad instead of .long is used for address for x32
Date: Thu, 21 Jul 2011 13:31:00 -0000	[thread overview]
Message-ID: <bug-49798-4-8dhsbbRMKQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49798-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49798

--- Comment #5 from Uros Bizjak <ubizjak at gmail dot com> 2011-07-21 13:30:22 UTC ---
(In reply to comment #4)

> > Linker should put correct address (so, zero extended 32bit address) here.
> 
> Did you mean assembler? In many cases, .quad is still simply wrong (PR 47446).

No, the linker. But looking at mentioned PR, linker is not able to generate
BFD_RELOC_64.

> GCC shouldn't generate .quad in this case.  A patch is posted at
> 
> http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01711.html

IMO, this patch is wrong. Generated code should look like the one for i686, so
it looks to me that check for Pmode != ptr_mode is missing somewhere in the
middle end.


  parent reply	other threads:[~2011-07-21 13:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 22:44 [Bug middle-end/49798] New: " hjl.tools at gmail dot com
2011-07-21  0:56 ` [Bug middle-end/49798] " hjl.tools at gmail dot com
2011-07-21  1:07 ` [Bug target/49798] " hjl.tools at gmail dot com
2011-07-21 10:26 ` ubizjak at gmail dot com
2011-07-21 13:10 ` hjl.tools at gmail dot com
2011-07-21 13:31 ` ubizjak at gmail dot com [this message]
2011-07-21 14:03 ` hjl.tools at gmail dot com
2011-07-21 15:54 ` hjl.tools at gmail dot com
2011-07-21 16:03 ` hjl.tools at gmail dot com
2011-07-21 16:26 ` ubizjak at gmail dot com
2011-07-21 16:33 ` hjl.tools at gmail dot com
2011-07-21 16:37 ` ubizjak at gmail dot com
2011-07-21 16:47 ` ubizjak at gmail dot com
2011-07-21 17:16 ` hjl.tools at gmail dot com
2011-07-21 17:19 ` hjl.tools at gmail dot com
2011-07-21 17:24 ` hjl.tools at gmail dot com
2011-07-21 20:00 ` hjl.tools at gmail dot com
2011-07-21 20:13 ` ubizjak at gmail dot com
2011-07-22 11:55 ` hjl.tools 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=bug-49798-4-8dhsbbRMKQ@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).