public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51931] New: No support for MIPS16 long branches Date: Sat, 21 Jan 2012 11:58:00 -0000 [thread overview] Message-ID: <bug-51931-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51931 Bug #: 51931 Summary: No support for MIPS16 long branches Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: rsandifo@gcc.gnu.org The MIPS port doesn't detect when MIPS16 branches are out of range, and it doesn't provide the same kind of "branch around jump" fallback as it does for non-MIPS16 code. This has always been a problem, and shows up as a long-standing failure in gcc.c-torture/compile/20001226-1.c and g++.dg/opt/longbranch1.C. I've thought about various fixes, such as saving a MIPS16 register to $1 before using it as a scratch, then restoring it in the branch delay slot. But there are various ugly cases. The bug only triggers for very large functions and at least these days there's a workaround: add __attribute__((nomips16)).
next reply other threads:[~2012-01-21 11:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-21 11:58 rsandifo at gcc dot gnu.org [this message] 2012-01-22 12:12 ` [Bug target/51931] " rsandifo at gcc dot gnu.org 2012-01-22 17:11 ` rsandifo at gcc dot gnu.org 2012-08-02 21:32 ` rsandifo at gcc dot gnu.org 2015-08-05 14:41 ` rsandifo 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-51931-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: 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).