This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug middle-end/30774] [4.1 regression] ld: fatal: too many symbols require `small' PIC references



------- Comment #2 from ghazi at gcc dot gnu dot org  2007-02-12 14:56 -------
Correction, on 4.0.3 & 4.0.4, I get one error:
FAIL: tmpdir-gcc.dg-struct-layout-1/t002 c_compat_x_tst.o-c_compat_y_tst.o link
http://gcc.gnu.org/ml/gcc-testresults/2006-03/msg00732.html
http://gcc.gnu.org/ml/gcc-testresults/2007-02/msg00185.html


As I noted here:
http://gcc.gnu.org/ml/gcc/2007-02/msg00211.html

exactly one of the three sparc32 errors arose between June 18 and June 22, 2006
on the 4.1 branch.  Here are the testsuite posts:

http://gcc.gnu.org/ml/gcc-testresults/2006-06/msg01003.html
http://gcc.gnu.org/ml/gcc-testresults/2006-06/msg01167.html

So far only the fortran one regressed between those dates, the C and C++
sparc32 errors were already there on the 18th.  It doesn't seem to be any one
particular patch that causes the overall problem since they didn't all happen
at the same time.  But I'd like to understand why these are getting worse.


-- 

ghazi at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|4.0.4                       |


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]