public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58523] ARM and AArch64:  -fsection-anchors doesn't seem to work
Date: Wed, 25 Sep 2013 06:30:00 -0000	[thread overview]
Message-ID: <bug-58523-4-eqLkiPRxVw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58523-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
With -fno-common,
arm LE produces:
    movw    r3, #:lower16:.LANCHOR0
    movt    r3, #:upper16:.LANCHOR0
    ldmia    r3, {r0, r3}
    add    r0, r0, r3
    bx    lr

AARCH64 produces:
    adrp    x1, .LANCHOR0
    add    x1, x1, :lo12:.LANCHOR0
    ldr    w2, [x1]
    ldr    w0, [x1,4]
    add    w0, w2, w0
    ret


  parent reply	other threads:[~2013-09-25  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  6:20 [Bug target/58523] New: " b.grayson at samsung dot com
2013-09-25  6:28 ` [Bug target/58523] " pinskia at gcc dot gnu.org
2013-09-25  6:29 ` pinskia at gcc dot gnu.org
2013-09-25  6:30 ` pinskia at gcc dot gnu.org [this message]
2013-09-25  6:55 ` b.grayson at samsung 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-58523-4-eqLkiPRxVw@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).