public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "droopycom at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14895] New: soft float flags missings from libgcc.a (and others)
Date: Thu, 08 Apr 2004 19:55:00 -0000	[thread overview]
Message-ID: <20040408195515.14895.droopycom@yahoo.com> (raw)

Hi,

I experienced this trying to compile a uClinux arm kernel with arm-elf-gcc 
3.3.3. The kernel link will complain that libgcc.a uses hard float while linux 
kernel uses soft-floats. arm-elf-objdump -p shows that the linux object files 
have the SOFTFLOAT flag while libgcc doesnt. Linux CFLAGS include "-msoft-
float", but I believe libgcc was compiled without this flag but the default is 
soft float anyway. The problem is that gas doesnt receive the correct flags 
when called.
The following simple patch to gcc solved my particular issue:

### soft float patch
--- gcc-3.3-branch/gcc/config/arm/elf.h	2004-03-30 12:43:45.000000000 -0800
+++ gcc-3.3.3-fg/gcc/config/arm/elf.h	2004-04-07 21:42:05.000000000 -0700
@@ -46,7 +46,7 @@ Boston, MA 02111-1307, USA.  */
 
 #ifndef SUBTARGET_ASM_FLOAT_SPEC
 #define SUBTARGET_ASM_FLOAT_SPEC "\
-%{mapcs-float:-mfloat} %{msoft-float:-mno-fpu}"
+%{mapcs-float:-mfloat} %{!mhard-float:-mfpu=softfpa} %{mhard-float:-mfpu=fpa}" 
 #endif
 
 #ifndef ASM_SPEC
##### End patch

However I found a more complete patch and analysis of the problem by Nick 
Clifton in the archives:
http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00593.html

Apparently, theres no bug filed for this, nor the patch made it into the 3.3 
branch.

I also believe that one work around would be to remove the -msoft-float from 
the linux CFLAGS, although I patched my gcc first so I didnt really test.

Thanks

-- F.G.

-- 
           Summary: soft float flags missings from libgcc.a (and others)
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: droopycom at yahoo dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: all
  GCC host triplet: all
GCC target triplet: arm-elf


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


             reply	other threads:[~2004-04-08 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 19:55 droopycom at yahoo dot com [this message]
2004-04-08 23:25 ` [Bug target/14895] " pinskia at gcc dot gnu dot org
2004-04-18  2:24 ` droopycom at yahoo dot com
2004-04-18  3:21 ` pinskia at gcc dot gnu dot org
2004-06-18 21:28 ` droopycom at yahoo dot com

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=20040408195515.14895.droopycom@yahoo.com \
    --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).