public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54854] New: [avr] Deprecate and finally remove the -mshort-calls command line option
Date: Mon, 08 Oct 2012 06:51:00 -0000	[thread overview]
Message-ID: <bug-54854-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 54854
           Summary: [avr] Deprecate and finally remove the -mshort-calls
                    command line option
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: gjl@gcc.gnu.org
        ReportedBy: gjl@gcc.gnu.org
            Target: avr


-mshort-calls uses RJMP/RCALL regardless of the flash size of the target
device.  This will lead to a linker error if a JMP/CALL target is out of reach
of RJMP/RCALL:

file.c:(.text+0x1234): relocation truncated to fit: R_AVR_13_PCREL against
symbol `function' defined in in module.o

The -mshort-calls option dates back to the times before the linker could relax
JMP/CALL to RJMP/RCALL if the jump offset allows this.

The above error message is a blocker and hard to understand for users.

Instead of -mstort-calls, the compiler can be called with -mrelax or
-Wl,--relax to direct the linker to use the shortest possible instruction.


             reply	other threads:[~2012-10-08  6:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08  6:51 gjl at gcc dot gnu.org [this message]
2012-10-08  6:52 ` [Bug target/54854] " gjl at gcc dot gnu.org
2012-10-08 10:14 ` gjl at gcc dot gnu.org
2012-10-08 10:27 ` gjl at gcc dot gnu.org
2012-10-10 21:47 ` gjl at gcc dot gnu.org

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-54854-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).