public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thomas at koeller dot dyndns dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/12476] New: ARM/THUMB thunk calls broken Date: Wed, 01 Oct 2003 11:27:00 -0000 [thread overview] Message-ID: <20031001112729.12476.thomas@koeller.dyndns.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12476 Summary: ARM/THUMB thunk calls broken Product: gcc Version: 3.3.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: thomas at koeller dot dyndns dot org CC: gcc-bugs at gcc dot gnu dot org,thomas dot koeller at baslerweb dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: arm-ecos-elf When compiling ARM programs in THUMB mode, thunks use a 'b' instruction to branch to the target function. Since the 'b' instruction has a very limited adressing range (+/- 256 bytes), and the thunk and its target function are placed in different sections, linking errors are very common: csr_camerastatus.o: In function `non-virtual thunk [nv:-24] to CSR_CAMERASTATUS::SetProtocolError(ProtocolErrorHandler::EPROT_ERR_VAL)': csr_camerastatus.o(.gnu.linkonce.t._ZThn24_N16CSR_CAMERASTATUS16SetProtocolErrorEN20ProtocolErrorHandler13EPROT_ERR_VALE+0x2): relocation truncated to fit: R_ARM_THM_PC11 CSR_CAMERASTATUS::SetProtocolError(ProtocolErrorHandler::EPROT_ERR_VAL)
next reply other threads:[~2003-10-01 11:27 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-01 11:27 thomas at koeller dot dyndns dot org [this message] 2003-10-01 17:52 ` [Bug target/12476] " pinskia at gcc dot gnu dot org 2003-10-01 18:31 ` pinskia at gcc dot gnu dot org 2003-10-01 18:31 ` pinskia at gcc dot gnu dot org 2003-10-01 19:19 ` rearnsha at gcc dot gnu dot org 2003-11-23 5:45 ` cvs-commit at gcc dot gnu dot org 2004-01-09 2:47 ` pinskia at gcc dot gnu dot org 2004-01-09 10:25 ` rearnsha at gcc dot gnu dot org 2004-01-14 3:39 ` pinskia at gcc dot gnu dot org 2004-01-14 5:41 ` pinskia at gcc dot gnu dot org 2004-01-14 9:21 ` rearnsha at gcc dot gnu dot org 2004-01-14 9:40 ` pinskia at gcc dot gnu dot org 2004-02-03 14:44 ` cvs-commit at gcc dot gnu dot org 2004-02-03 14:45 ` cvs-commit at gcc dot gnu dot org 2004-02-03 16:39 ` pinskia at gcc dot gnu dot org 2004-02-03 16:50 ` rearnsha at gcc dot gnu dot org 2004-02-05 16:07 ` cvs-commit at gcc dot gnu dot org 2004-02-12 17:55 ` ian at wasabisystems 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=20031001112729.12476.thomas@koeller.dyndns.org \ --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: linkBe 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).