public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: ng@piments.com
To: Martin Guy <martinwguy@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: -mfloat-abi=softfp
Date: Tue, 27 Apr 2010 12:58:00 -0000	[thread overview]
Message-ID: <4BD6DF79.2050705@piments.com> (raw)
In-Reply-To: <h2s56d259a01004270407i3deb815cqe2174c85a5ed077@mail.gmail.com>

On 04/27/10 13:07, Martin Guy wrote:
> On 4/27/10, ng@piments.com<ng@piments.com>  wrote:
>>   So now  I've put
>>    LIBC_GLIBC_EXTRA_CFLAGS= -mfpu=maverick -mfloat-abi=softfp  -mcpu=ep9312
>>
>>   It's throwing ICE in glibc.:
>>
>>   [ALL  ]    ibm420.c:1: warning: switch -mcpu=ep9312 conflicts with -march=
>> switch
>>   [ALL  ]    ../iconv/skeleton.c: In function 'gconv':
>>   [ERROR]    ../iconv/skeleton.c:801: internal compiler error: Segmentation
>> fault
>>   [ALL  ]    Please submit a full bug report,
>>   [ALL  ]    with preprocessed source if appropriate.
>
> ICE is a bug in the GCC that you are using to build the cross-compiler
> - the "core compiler" - in this case, the output of your stage1
> compilation. "Segmentation fault" is pretty severe :(
> To investigate further where it is segfaulting you can run the one
> specific command under gdb. I the core compiler is built using the
> system glibc, so it shouldn't be a bug in the glibc patches. For what
> it's worth, I've used the native gcc-4.3-crunch to build glibc again.
> natively).
>
> Another strategy you could use is to build gcc-4.2, which runs faster,
> uses less memory to compile things and produces smaller and faster
> code than gcc-4.3 (yes, really!)
>
>>    warning: switch -mcpu=ep9312 conflicts with -march= switch
>>   I have left -mcpu -mtune empty in menuconfig giving just -march=armv4t
>
> -march=ep9312 should be what you need, but I doubt that will fix the ICE.
>
>      M
>
Thanks Martin,

Uptil now I was using -march=armv4t , setting it ep9312 fails on 4.2.4


[ALL  ]    /back/ts/ct-ng/targets/src/gcc-4.2.4/gcc/crtstuff.c:1: 
warning: target CPU does not support interworking
[ALL  ]    Assembler messages:
[ALL  ]    Error: unknown architecture `ep9312'
[ALL  ]
[ALL  ]    Error: unrecognized option -march=ep9312

man gcc (4.3.4) says:

`-march=NAME'
      This specifies the name of the target ARM architecture.  GCC uses
      this name to determine what kind of instructions it can emit when
      generating assembly code.  This option can be used in conjunction
      with or instead of the `-mcpu=' option.  Permissible names are:
      `armv2', `armv2a', `armv3', `armv3m', `armv4', `armv4t', `armv5',
      `armv5t', `armv5te', `armv6', `armv6j', `armv6t2', `armv6z',
      `armv6zk', `armv7', `armv7-a', `armv7-r', `armv7-m', `iwmmxt',
      `ep9312'.

:?
I did not try this config with 4.3.4.

Could this relate to the -march= switch message I was getting before. Is 
some other stage deciding this is invalid and replacing it with a null 
string?

Now trying your suggestion of 4.2.4

thx

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2010-04-27 12:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18 18:39 -mfloat-abi=softfp ng
2010-04-18 18:58 ` -mfloat-abi=softfp Martin Guy
2010-04-19  1:22   ` -mfloat-abi=softfp ng
2010-04-19  9:52     ` -mfloat-abi=softfp Martin Guy
2010-04-19  9:53       ` -mfloat-abi=softfp Martin Guy
2010-04-19 17:53         ` -mfloat-abi=softfp ng
2010-04-19 18:16           ` -mfloat-abi=softfp Martin Guy
2010-04-19 18:21           ` -mfloat-abi=softfp Martin Guy
2010-04-27 10:13       ` -mfloat-abi=softfp ng
2010-04-27 11:08         ` -mfloat-abi=softfp Martin Guy
2010-04-27 12:58           ` ng [this message]
     [not found]             ` <v2j56d259a01004270621i6e44dbb2p87cc64e96b5c6032@mail.gmail.com>
2010-04-27 18:55               ` -mfloat-abi=softfp ng
2010-04-27 13:27           ` -mfloat-abi=softfp ng
2010-04-27 15:25             ` -mfloat-abi=softfp Martin Guy
     [not found]               ` <4BD7CBFD.8010702@piments.com>
     [not found]                 ` <q2v56d259a01004280152t2d59959ah57cdf11440f63c06@mail.gmail.com>
2010-04-29 20:20                   ` -mfloat-abi=softfp ng

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=4BD6DF79.2050705@piments.com \
    --to=ng@piments.com \
    --cc=crossgcc@sourceware.org \
    --cc=martinwguy@gmail.com \
    /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).