public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20633] libgcc2.c:1623: error: size of array 'compile_type_assert' is negative
Date: Sun, 17 Apr 2005 21:13:00 -0000	[thread overview]
Message-ID: <20050417211344.1025.qmail@sourceware.org> (raw)
In-Reply-To: <20050325041046.20633.gerald@pfeifer.com>


------- Additional Comments From ebotcazou at gcc dot gnu dot org  2005-04-17 21:13 -------
It's a target problem: FreeBSD overrides this line from sparc.h:

#define CPP_SPEC "%(cpp_cpu) %(cpp_arch) %(cpp_endian) %(cpp_subtarget)"

with this line from freebsd-spec.h:

/* Provide a CPP_SPEC appropriate for FreeBSD.  We just deal with the GCC 
   option `-posix', and PIC issues.  */

#define FBSD_CPP_SPEC "							\
  %(cpp_cpu)								\
  %{fPIC|fpic|fPIE|fpie:-D__PIC__ -D__pic__}				\
  %{posix:-D_POSIX_SOURCE}"

The missing bits are %(cpp_arch).  Also note the bogus quotation in the spec.

I think it's up to the FreeBSD maintainer to decide what is the best long-term
fix.  For 4.0.0, something like:

#undef  CPP_SPEC
#define CPP_SPEC \
  %(cpp_cpu)								\
  %(cpp_arch)								\
  %{fPIC|fpic|fPIE|fpie:-D__PIC__ -D__pic__}				\
  %{posix:-D_POSIX_SOURCE}

in config/sparc/freebsd.h should be good enough.

Gerald, if it works for you, I can approve it on principle for the 4.0 branch
and I think you can ask Mask permission for installing it before 4.0RC2.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|bootstrap                   |target


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


  parent reply	other threads:[~2005-04-17 21:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25  4:10 [Bug bootstrap/20633] New: sparc64-portbld-freebsd5.3: " gerald at pfeifer dot com
2005-04-15 22:20 ` [Bug bootstrap/20633] " ebotcazou at gcc dot gnu dot org
2005-04-15 22:21 ` [Bug bootstrap/20633] " ebotcazou at gcc dot gnu dot org
2005-04-17 21:13 ` ebotcazou at gcc dot gnu dot org [this message]
2005-04-18  9:24 ` [Bug target/20633] " ebotcazou at gcc dot gnu dot org
2005-04-24 22:57 ` gerald at pfeifer dot com
2005-04-30 20:38 ` cvs-commit at gcc dot gnu dot org
2005-04-30 20:52 ` gerald at pfeifer dot com
2005-04-30 21:08 ` [Bug target/20633] [4.0 only] " pinskia at gcc dot gnu dot org
2005-05-01 18:11 ` cvs-commit at gcc dot gnu dot org
2005-05-01 18:12 ` gerald at pfeifer dot com
2005-05-01 18:59 ` cvs-commit 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=20050417211344.1025.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).