public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <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 08:52:00 -0000	[thread overview]
Message-ID: <bug-64833-4-4euSw8GodH@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 #13 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Kazumoto Kojima from comment #12)
> I could reproduce the problem on trunk with '-DXS_VERSION=\"6.89\" -fwrapv
> -fno-strict-aliasing -fopenmp -O2 -fstack-protector-strong -fexceptions
> -fPIC'
> with the cross sh4-unknown-linux-gnu compiler.

Indeed, the bug is still there [1]:

gcc -std=gnu99 -c  -I../ -I.. -I/usr/include/X11 -I/usr/include/freetype2
-I/usr/include/libxml2 -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -mieee -fwrapv
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -fopenmp -Wall -g -fno-strict-aliasing -O2 -Wall
-pthread -O2 -g   -DVERSION=\"1.3.20\" -DXS_VERSION=\"1.3.20\" -fPIC
"-I/usr/lib/sh4-linux-gnu/perl/5.20/CORE"  -D_FILE_OFFSET_BITS=64
-D_LARGE_FILES=1 -DHAVE_CONFIG_H Magick.c
(...)
Magick.c: At top level:
Magick.xs:247:4: warning: 'LogEventTypes' defined but not used
[-Wunused-variable]
   *LogEventTypes[] =
    ^
{standard input}: Assembler messages:
{standard input}:15085: Error: pcrel too far
{standard input}:15086: Error: pcrel too far
make[2]: *** [Magick.o] Error 1

Adrian

> [1] http://buildd.debian-ports.org/status/fetch.php?pkg=graphicsmagick&arch=sh4&ver=1.3.20-3%2Bdeb8u1&stamp=1435541933


  parent reply	other threads:[~2015-06-29  8:52 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 [this message]
2015-06-29 14:48 ` olegendo at gcc dot gnu.org
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-4euSw8GodH@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: link
Be 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).