public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/30774] [4.1 regression] ld: fatal: too many symbols require `small' PIC references
Date: Mon, 12 Feb 2007 15:22:00 -0000	[thread overview]
Message-ID: <20070212152226.25286.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30774-578@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from ghazi at gcc dot gnu dot org  2007-02-12 15:22 -------
Hmm on June *15th*, the -fbounds-check flag was added to the fortran testcase
gfortran.dg/cray_pointers_2.f90, and taking that flag out of today's sources
allows the testcase to pass with -fpic.

However clearly my checkout on the *18th* (which had -fbounds-check on it) the
testcase somehow passed as well.  So I don't think adding that flag was the
actual cause of this failure.  But it certainly affects the number of symbols
drastically.


-- 


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


  parent reply	other threads:[~2007-02-12 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 14:37 [Bug middle-end/30774] New: " ghazi at gcc dot gnu dot org
2007-02-12 14:39 ` [Bug middle-end/30774] " ghazi at gcc dot gnu dot org
2007-02-12 14:57 ` ghazi at gcc dot gnu dot org
2007-02-12 15:22 ` ghazi at gcc dot gnu dot org [this message]
2007-02-21 15:23 ` rguenth at gcc dot gnu dot org
2008-07-04 16:00 ` [Bug middle-end/30774] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-07-10 13:41 ` jakub at gcc dot gnu dot org
2008-07-30 15:05 ` jakub at gcc dot gnu dot org
2009-03-31 20:07 ` [Bug middle-end/30774] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:35 ` rguenth at gcc dot gnu dot org
2010-05-22 18:18 ` [Bug middle-end/30774] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org
2010-09-20 22:08 ` ebotcazou at gcc dot gnu dot org

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=20070212152226.25286.qmail@sourceware.org \
    --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).