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

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

            Bug ID: 58523
           Summary: ARM and AArch64:  -fsection-anchors doesn't seem to
                    work
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: b.grayson at samsung dot com
            Target: arm, aarch64
             Build: gcc-4.9-20130915-arm-linux-gnueabhihf,
                    gcc-aarch64-4.9-20130602/aarch64-linux-gnu-gcc

Created attachment 30890
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30890&action=edit
Test C file with two global variables, and a use of both of them

I've tried compiling with -fsection-anchors in several different releases of
gcc for ARM and now for aarch64, and it seems the optimization is not kicking
in for scenarios where it should.  I looked through the gcc/config directories,
and the support seems to be there.  Here is a simple testcase.  The resulting
assembly (not posted here, according to bug-reporting guidelines) does a full
address-generation for variable a, and then again for variable b.


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  6:20 b.grayson at samsung dot com [this message]
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
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@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).