public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55195] [4.8 Regression] shorten_branches generates incorrect forward branch distances Date: Thu, 06 Dec 2012 02:20:00 -0000 [thread overview] Message-ID: <bug-55195-4-GsPRjTu1eS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55195-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55195 --- Comment #19 from John David Anglin <danglin at gcc dot gnu.org> 2012-12-06 02:19:57 UTC --- Author: danglin Date: Thu Dec 6 02:19:48 2012 New Revision: 194238 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194238 Log: Backport for mainline: 2011-11-30 John David Anglin <dave.anglin@nrc-cnrc.gc.ca> PR middle-end/50283 * config/pa/pa.md (in_branch_delay): Disallow frame related insns. (in_nullified_branch_delay): Likewise. (in_call_delay): Likewise. 2012-11-12 John David Anglin <dave.anglin@nrc-cnrc.gc.ca> PR target/55195 * config/pa/pa.md (type): Add sibcall and sh_func_adrs insn types. (in_branch_delay): Don't allow sibcall or sh_func_adrs insns. (in_nullified_branch_delay): Likewise. (in_call_delay): Likewise. Define delay for sibcall insns. Adjust Z3 and Z4 insn reservations for new types. Add opaque cond to mark all calls, sibcalls, dyncalls and the $$sh_func_adrs call as variable. Update type of sibcalls and $$sh_func_adrs call. * config/pa/pa.c (pa_adjust_insn_length): Revise to return updated length instead of adjustment. Handle negative and undefined call adjustments for insn_default_length. Remove adjustment for millicode insn with unfilled delay slot. (pa_output_millicode_call): Update for revised millicode length. * config/pa/pa.h (ADJUST_INSN_LENGTH): Revise to set LENGTH. 2012-12-05 John David Anglin <dave.anglin@nrc-cnrc.gc.ca> * config/pa/pa.md: Use "const_int 0" instead of match_test to simplify opaque cond in all call insns. Modified: branches/gcc-4_6-branch/gcc/ChangeLog branches/gcc-4_6-branch/gcc/config/pa/pa.c branches/gcc-4_6-branch/gcc/config/pa/pa.h branches/gcc-4_6-branch/gcc/config/pa/pa.md
prev parent reply other threads:[~2012-12-06 2:20 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-03 17:05 [Bug middle-end/55195] New: " danglin at gcc dot gnu.org 2012-11-03 20:45 ` [Bug middle-end/55195] " amylaar at gcc dot gnu.org 2012-11-04 2:52 ` dave.anglin at bell dot net 2012-11-04 16:59 ` amylaar at gcc dot gnu.org 2012-11-04 17:32 ` [Bug target/55195] " amylaar at gcc dot gnu.org 2012-11-04 17:35 ` amylaar at gcc dot gnu.org 2012-11-04 22:23 ` dave.anglin at bell dot net 2012-11-04 23:50 ` dave.anglin at bell dot net 2012-11-05 2:32 ` amylaar at gcc dot gnu.org 2012-11-05 16:21 ` [Bug middle-end/55195] " amylaar at gcc dot gnu.org 2012-11-06 12:26 ` dave.anglin at bell dot net 2012-11-06 15:41 ` amylaar at gcc dot gnu.org 2012-11-06 17:25 ` amylaar at gcc dot gnu.org 2012-11-07 0:39 ` dave.anglin at bell dot net 2012-11-07 0:54 ` amylaar at gcc dot gnu.org 2012-11-11 18:09 ` danglin at gcc dot gnu.org 2012-11-13 0:37 ` [Bug target/55195] " danglin at gcc dot gnu.org 2012-11-13 1:11 ` danglin at gcc dot gnu.org 2012-12-01 20:36 ` danglin at gcc dot gnu.org 2012-12-06 2:20 ` danglin at gcc dot gnu.org [this message]
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-55195-4-GsPRjTu1eS@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).