public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64833] [SH]: Error: pcrel too far when compiling imagemagick and graphicsmagick on Debian sh4 Date: Mon, 29 Jun 2015 14:48:00 -0000 [thread overview] Message-ID: <bug-64833-4-8OTqdTJOVX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64833-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64833 --- Comment #14 from Oleg Endo <olegendo at gcc dot gnu.org> --- (In reply to Kazumoto Kojima from comment #12) > diff --git a/config/sh/sh.c b/config/sh/sh.c > index 0139095..86cbea7 100644 > --- a/config/sh/sh.c > +++ b/config/sh/sh.c > @@ -5261,6 +5261,11 @@ find_barrier (int num_mova, rtx_insn *mova, rtx_insn > *from) > && GET_CODE (PATTERN (from)) == UNSPEC_VOLATILE > && XINT (PATTERN (from), 1) == UNSPECV_CONST_END) > return from; > + /* get_attr_length might return the length of the original worker > + for casesi_worker_2. Get uncached length for it. */ > + else if (NONJUMP_INSN_P (from) > + && recog_memoized (from) == CODE_FOR_casesi_worker_2) > + inc = insn_default_length (from); > > if (BARRIER_P (from)) > { I was trying to understand what's happening there ... it's a bit confusing. A cleaner way would probably be to add a function in final.c to update the cached length value for the INSN_UID in final.c. Then, invoke that function for the insn in fixup_mova when the pattern rtx is changed from casesi_worker_1 to casesi_worker_2. However, I guess that all the other insn length dependent values will have to be re-calculated to get a consistent state. Wouldn't it be easier/safer to just set the length of casesi_worker_1 to "8"? >From gcc-bugs-return-490966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jun 29 14:56:50 2015 Return-Path: <gcc-bugs-return-490966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 38327 invoked by alias); 29 Jun 2015 14:56:49 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 38278 invoked by uid 48); 29 Jun 2015 14:56:44 -0000 From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66563] [4.9 Regression] ICE (segmentation fault) on sh4-linux-gnu Date: Mon, 29 Jun 2015 14:56:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: olegendo at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-66563-4-0jdxdZHpoB@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66563-4@http.gcc.gnu.org/bugzilla/> References: <bug-66563-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-06/txt/msg03298.txt.bz2 Content-length: 149 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf563 --- Comment #39 from Oleg Endo <olegendo at gcc dot gnu.org> --- Can we close this PR as fixed?
next prev parent reply other threads:[~2015-06-29 14:48 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-28 11:50 [Bug c/64833] New: " glaubitz at physik dot fu-berlin.de 2015-02-15 21:29 ` [Bug c/64833] " olegendo at gcc dot gnu.org 2015-02-15 22:12 ` [Bug target/64833] " olegendo at gcc dot gnu.org 2015-02-15 22:44 ` glaubitz at physik dot fu-berlin.de 2015-02-25 20:12 ` olegendo at gcc dot gnu.org 2015-02-25 20:33 ` glaubitz at physik dot fu-berlin.de 2015-03-15 11:44 ` glaubitz at physik dot fu-berlin.de 2015-06-28 13:18 ` olegendo at gcc dot gnu.org 2015-06-28 15:16 ` glaubitz at physik dot fu-berlin.de 2015-06-28 15:24 ` glaubitz at physik dot fu-berlin.de 2015-06-29 5:07 ` olegendo at gcc dot gnu.org 2015-06-29 5:45 ` kkojima at gcc dot gnu.org 2015-06-29 8:52 ` glaubitz at physik dot fu-berlin.de 2015-06-29 14:48 ` olegendo at gcc dot gnu.org [this message] 2015-06-29 23:36 ` kkojima at gcc dot gnu.org 2015-06-30 0:32 ` kkojima at gcc dot gnu.org 2015-06-30 2:37 ` olegendo at gcc dot gnu.org 2015-06-30 2:39 ` olegendo at gcc dot gnu.org 2015-06-30 3:56 ` kkojima at gcc dot gnu.org 2015-07-01 1:03 ` kkojima at gcc dot gnu.org 2015-07-01 22:01 ` kkojima at gcc dot gnu.org 2015-07-01 22:05 ` kkojima at gcc dot gnu.org 2015-07-01 22:43 ` kkojima at gcc dot gnu.org 2015-07-19 15:09 ` glaubitz at physik dot fu-berlin.de
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-64833-4-8OTqdTJOVX@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).