public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Pearse <peter.pearse@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FW:  [PATCH][ARM] Rationalize ARM compiler options
Date: Mon, 18 Feb 2008 09:20:18 -0000	[thread overview]
Message-ID: <000301c8720f$7abea710$9a4d010a@Emea.Arm.com> (raw)


> -----Original Message-----
> From: Peter Pearse [mailto:peter.pearse at arm.com] 
> Sent: 14 February 2008 13:59
> To: 'wd at denx.de'
> Subject: RE: [U-Boot-Users] [PATCH][ARM] Rationalize ARM 
> compiler options
> 
> 
> > -----Original Message-----
> > From: wd at denx.de [mailto:wd at denx.de]
> > Sent: 13 February 2008 22:51
> > To: Peter Pearse
> > Cc: U-Boot-Users
> > Subject: Re: [U-Boot-Users] [PATCH][ARM] Rationalize ARM compiler 
> > options
> > 
> > 
> > Please don't add too many empty lines.
> >
> 
> OK - I'll change thie when I re-submit. 
> I just like to be able to ripple thru my buffers to animate 
> the differences between almost identical files.
>  
> > Why exactly are you dropping -msoft-float here?
> 
> I was under the delusion that dropping this protected against 
> incorporation of floating point instructions. 
> 
> Have I now got a clear understanding of the position:-
> 
> "
> The use of floating point arithmetic in the U-Boot code is 
> deprecated. 
> However the ELDK toolchains provide floating point support 
> and were built with the -msoft-float option. This option is 
> supplied to the code to ensure any floating point arithmetic 
> included links in the floating point support code correctly. 
> " 
> 
> If so I'll put -msoft-float in all arm config.mk files.
> 
> > 
> > > -# Make ARMv5 to allow more compilers to work, even though its v6.
> > > -PLATFORM_CPPFLAGS += -march=armv5
> > > +PLATFORM_CPPFLAGS += -march=armv6
> > 
> > Why exactly are you changing this?
> 
> arm1136 is an ARM Architecture V6 processor.
> 
> My position is:
> "
> The main (arm) tree processor options should use the correct 
> architecture option for the processor (provided this option 
> is accepted without error or warning  by the ELDK arm 
> toolchains) Users using compilers which do not support the 
> correct architecture should be made aware of this.
> Should they wish to use another compiler they can change this 
> option locally.  
> "
> 
> I would also accept
> (reluctantly, although it saves lots of space I could waste 
> as empty lines ;-) )
> 
> "
> For simplicity, the main (arm) tree processor options use the 
> lowest common architecture option (armv4), whatever the 
> processor implements. Users can change this option locally.  
> "
> 
> At present we have a mixture.....
> 
> Regards
> 
> Peter
> 
> 

             reply	other threads:[~2008-02-18  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18  9:20 Peter Pearse [this message]
2008-02-18 11:33 ` [U-Boot-Users] FW: [PATCH][ARM] Rationalize ARM compiler options Haavard Skinnemoen
2008-02-18 12:19   ` Wolfgang Denk
2008-02-18 23:04 ` Ulf Samuelsson
2008-02-19 12:36   ` Wolfgang Denk
2008-02-20  6:33     ` Ulf Samuelsson
2008-02-20  9:55       ` Haavard Skinnemoen
2008-02-20 17:58         ` Ulf Samuelsson
2008-02-20 19:28           ` Haavard Skinnemoen
     [not found] <011a01c87359$34cbbc70$050514ac@atmel.com>
2008-02-20  9:25 ` Peter Pearse
2008-02-20 17:42   ` Ulf Samuelsson

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='000301c8720f$7abea710$9a4d010a@Emea.Arm.com' \
    --to=peter.pearse@arm.com \
    --cc=u-boot@lists.denx.de \
    /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