public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org To: avbidder@acter.ch, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rearnsha@gcc.gnu.org Subject: Re: target/4863: arm/thumb: code for switch statements: branch out of range Date: Sun, 17 Mar 2002 07:57:00 -0000 [thread overview] Message-ID: <20020317155720.9120.qmail@sources.redhat.com> (raw) Synopsis: arm/thumb: code for switch statements: branch out of range Responsible-Changed-From-To: unassigned->rearnsha Responsible-Changed-By: rearnsha Responsible-Changed-When: Sun Mar 17 07:57:19 2002 Responsible-Changed-Why: Patch in progress. We shouldn't be using branch instructions for thumb pic. It works ok for arm, but is unsuitable for thumb, not least because the dispatch code assumes that each entry in the table will be four bytes, but a thumb branch instruction is only two. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4863
next reply other threads:[~2002-03-17 15:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-17 7:57 rearnsha [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-18 5:48 rearnsha 2001-11-01 23:58 avbidder
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=20020317155720.9120.qmail@sources.redhat.com \ --to=rearnsha@gcc.gnu.org \ --cc=avbidder@acter.ch \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).