public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63842] x86-64 large PIC model may load the GOT base into the wrong register
Date: Thu, 27 Nov 2014 21:30:00 -0000	[thread overview]
Message-ID: <bug-63842-4-bzoQUyMJot@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63842-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63842

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-11-27
     Ever confirmed|0                           |1

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
r218132 generates:

main:
.LFB11:
    .cfi_startproc
.L2:
    leaq    .L2(%rip), %rax
    movabsq    $_GLOBAL_OFFSET_TABLE_-.L2, %r11
    movabsq    $.LC0@GOTOFF, %rdx
    pushq    %r15
    .cfi_def_cfa_offset 16
    .cfi_offset 15, -16
    addq    %r11, %rax
    leaq    (%rax,%rdx), %rdi
    movabsq    $puts@PLTOFF, %rdx
    movq    %rax, %r15
    addq    %rax, %rdx
    call    *%rdx
    xorl    %eax, %eax
    popq    %r15
    .cfi_def_cfa_offset 8
    ret
    .cfi_endproc
.LFE11:

It looks OK.  But it is hard to test without a linker supporting large
model PLT.  I will leave it open until I finish large model PLT support
in binutils so that I can verify it.


  parent reply	other threads:[~2014-11-27 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 23:34 [Bug target/63842] New: " hjl.tools at gmail dot com
2014-11-12 23:41 ` [Bug target/63842] " hjl.tools at gmail dot com
2014-11-27 21:30 ` hjl.tools at gmail dot com [this message]
2021-08-09  7:33 ` pinskia at gcc dot gnu.org
2021-08-09 12:40 ` 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-63842-4-bzoQUyMJot@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).