public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PowerPC -mrelocatable
Date: Fri, 11 Sep 2009 17:52:03 -0500	[thread overview]
Message-ID: <1252709523.28829.105.camel@localhost.localdomain> (raw)
In-Reply-To: <20090908182055.6DC71832E8DE@gemini.denx.de>

Hi Wolfgang,

> > Does anyone out there by chance have a failure case for gcc > 4.0.0,
> > because I can't seem to reproduce the issues others had in the past.
> 
> Do you have an up-to-date patch that can be used for such testing?

I just sent an example patch (ppc: Relocation test patch) that others
can use (or quickly adapt) to test their board using relocation proper.
It'd be great if others could give any feedback on what impact this
patch has on their board.

> > My vote would be to find out which version of gcc contains the
> > relocation bug and spit out an error if gcc < than that version is used.
> 
> Agreed.
> 
> > We could also try and get fancy and dynamically turn on/off relocation
> > support at compile time based on gcc's version if other's wanted to
> > maintain support for older compilers.  These changes would only be for
> > ppc at this point btw.
> 
> I think there would be not  much  lost  if  we  dropped  support  for
> versions before gcc-4.x

I agree.  I believe 3.4.5 or 3.4.6 and later should work, but haven't
tested this hypothesis to any great degree.

I can generate a proper patch if the example patch doesn't break things
badly.

Best,
Peter

  parent reply	other threads:[~2009-09-11 22:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25  7:02 [U-Boot] Phy lib again Michal Simek
2009-08-25  7:08 ` Stefan Roese
2009-08-25  7:14   ` Michal Simek
2009-08-25 16:48     ` Ben Warren
2009-08-26  7:27       ` Michal Simek
2009-08-25  9:23   ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-26 20:13 ` [U-Boot] [RFC PATCH 1/3] net: rework the mii support Jean-Christophe PLAGNIOL-VILLARD
2009-08-26 20:13   ` [U-Boot] [RFC PATCH 2/3] net: add phylib implementation Jean-Christophe PLAGNIOL-VILLARD
2009-08-26 20:13     ` [U-Boot] [RFC PATCH 3/3] phylib: add generic phy driver Jean-Christophe PLAGNIOL-VILLARD
2009-08-27  1:58       ` Mike Frysinger
2009-08-27  1:55     ` [U-Boot] [RFC PATCH 2/3] net: add phylib implementation Mike Frysinger
2009-08-27  5:11       ` Stefan Roese
2009-08-27  5:54         ` Mike Frysinger
2009-08-27 15:38           ` Scott Wood
2009-08-27 15:56             ` Peter Tyser
2009-08-27 17:49               ` [U-Boot] PowerPC -mrelocatable Scott Wood
2009-08-27 19:36                 ` Joakim Tjernlund
2009-09-08 16:16                 ` Peter Tyser
2009-09-08 17:29                   ` Mike Frysinger
2009-09-08 18:20                   ` Wolfgang Denk
2009-09-09  8:04                     ` Joakim Tjernlund
2009-09-11 22:52                     ` Peter Tyser [this message]
2009-08-27 19:13             ` [U-Boot] [RFC PATCH 2/3] net: add phylib implementation Mike Frysinger
2009-08-27 19:16               ` Scott Wood
2009-08-27  1:16   ` [U-Boot] [RFC PATCH 1/3] net: rework the mii support Mike Frysinger
2009-08-27 15:44   ` Ben Warren

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=1252709523.28829.105.camel@localhost.localdomain \
    --to=ptyser@xes-inc.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