public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/43744]  New: SH: Error: pcrel too far
@ 2010-04-13  6:10 iwamatsu at nigauri dot org
  2010-04-13  6:12 ` [Bug c/43744] " iwamatsu at nigauri dot org
                   ` (10 more replies)
  0 siblings, 11 replies; 19+ messages in thread
From: iwamatsu at nigauri dot org @ 2010-04-13  6:10 UTC (permalink / raw)
  To: gcc-bugs

$ gcc-4.4 -c  -D_GNU_SOURCE -D_REENTRANT  -Wall -g -O2 -fPIC -DPIC db4.8-x.c
../dist/../lock/lock_deadlock.c: In function '__lock_detect':
../dist/../lock/lock_deadlock.c:123: warning: 'idmap' may be used uninitialized
in this function
../dist/../lock/lock_deadlock.c:124: warning: 'bitmap' may be used
uninitialized in this function
../dist/../lock/lock_deadlock.c:125: warning: 'nalloc' may be used
uninitialized in this function
../dist/../lock/lock_deadlock.c:125: warning: 'nlockers' may be used
uninitialized in this function
/tmp/cc8awAVe.s: Assembler messages:
/tmp/cc8awAVe.s:3023: Error: pcrel too far

gcc-4.1 and gcc-4.3 work fine.

$ gcc-4.4 -v
Using built-in specs.
Target: sh4-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.3-7'
--with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--enable-multiarch --enable-linker-build-id --with-system-zlib
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc
--with-multilib-list=m4,m4-nofpu --with-cpu=sh4 --enable-checking=release
--build=sh4-linux-gnu --host=sh4-linux-gnu --target=sh4-linux-gnu
Thread model: posix
gcc version 4.4.3 (Debian 4.4.3-7)

 gcc-4.4 (4.4.3-7) unstable; urgency=low
 .
   * Update to SVN 20100401 from the gcc-4_4-branch (r157925).
     - Fix PR libfortran/43517, PR tree-optimization/43528, PR target/43524,
       PR middle-end/43600, PR other/43562, PR target/39254,
       PR target/42113, PR c/43381, PR c++/41185, PR c++/41786,
       PR fortran/43409, PR fortran/43409, PR libfortran/43265,
       PR fortran/43551, PR libfortran/43605.


-- 
           Summary: SH: Error: pcrel too far
           Product: gcc
           Version: 4.4.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: iwamatsu at nigauri dot org
  GCC host triplet: sh4-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43744


^ permalink raw reply	[flat|nested] 19+ messages in thread
[parent not found: <bug-43744-4@http.gcc.gnu.org/bugzilla/>]

end of thread, other threads:[~2023-08-22 20:47 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-13  6:10 [Bug c/43744] New: SH: Error: pcrel too far iwamatsu at nigauri dot org
2010-04-13  6:12 ` [Bug c/43744] " iwamatsu at nigauri dot org
2010-04-13  6:35 ` [Bug target/43744] " kkojima at gcc dot gnu dot org
2010-04-13  6:56 ` kkojima at gcc dot gnu dot org
2010-04-13  8:09 ` iwamatsu at nigauri dot org
2010-04-13 10:29 ` rguenth at gcc dot gnu dot org
2010-04-15 11:55 ` kkojima at gcc dot gnu dot org
2010-04-16 22:34 ` kkojima at gcc dot gnu dot org
2010-04-22 22:03 ` kkojima at gcc dot gnu dot org
2010-05-05 22:12 ` kkojima at gcc dot gnu dot org
2010-05-05 22:28 ` kkojima at gcc dot gnu dot org
2010-05-05 22:46 ` kkojima at gcc dot gnu dot org
     [not found] <bug-43744-4@http.gcc.gnu.org/bugzilla/>
2014-08-30  0:22 ` kkojima at gcc dot gnu.org
2014-08-30  5:01 ` glaubitz at physik dot fu-berlin.de
2014-09-23 18:50 ` glaubitz at physik dot fu-berlin.de
2021-10-08 22:25 ` giulio.benetti at benettiengineering dot com
2021-10-08 22:26 ` giulio.benetti at benettiengineering dot com
2021-10-08 22:27 ` giulio.benetti at benettiengineering dot com
2023-08-22 20:47 ` giulio.benetti at benettiengineering dot com

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).