public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima 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 23:36:00 -0000 [thread overview] Message-ID: <bug-64833-4-QuoFzUxLQD@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 #15 from Kazumoto Kojima <kkojima at gcc dot gnu.org> --- (In reply to Oleg Endo from comment #14) > 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. The usual way to re-compute insn length is shorten_branches. I'm not sure that new function is a good idea or not. It looks a too big hammer for this corner case on one specific target. sh_reorg calls shorten_branches after the loop which includes find_barrier call and get_attr_length will return correct value after that. It looks too costly to call shorten_branches for the rare case in the loop. I'll look for another point to call shorten_branches which can fix the issue. > Wouldn't it be easier/safer to just set the length of casesi_worker_1 to "8"? It may be safest from the computational viewpoint, though it'll affect almost existing pic codes, I'm afraid. Perhaps it's OK for trunk. The above patch won't affect existing code except very limited cases, though it's a bit tricky.
next prev parent reply other threads:[~2015-06-29 23:36 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 2015-06-29 23:36 ` kkojima at gcc dot gnu.org [this message] 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-QuoFzUxLQD@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).