public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cmetcalf at tilera dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/17354] New: tile: signed dynamic relocations aren't handled correctly Date: Sat, 06 Sep 2014 16:22:00 -0000 [thread overview] Message-ID: <bug-17354-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17354 Bug ID: 17354 Summary: tile: signed dynamic relocations aren't handled correctly Product: glibc Version: 2.19 Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: cmetcalf at tilera dot com Target: tilegx, tilepro The tst-pie1 regression test fails on tile. The issue is that we're not properly handling signed relocations. The HWx_LAST relocations are loaded with "moveli", which sign-extends. Similarly the HW8 relocations tend to be for "movei" (sign-extending) and BrOff and JOff_Long are both sign-extending. A simple way to demonstrate the failure is to take two simple assembly programs like .global l1 l1: j l2 and a corresponding program with "l2: j l1", build them both without -fpic but as shared objects, and link them against a no-op main(). Trying to run the resulting program generates a "Relocation too large" failure, even though the l1 and l2 labels are quite close in memory. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-09-06 16:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-06 16:22 cmetcalf at tilera dot com [this message] 2014-09-06 16:30 ` [Bug dynamic-link/17354] " cvs-commit at gcc dot gnu.org 2014-09-06 16:32 ` cmetcalf at tilera 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-17354-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).