Re: [U-Boot] [PATCH] examples/standalone: Use gcc's -fno-toplevel-reorder

2010-10-12 Thread Wolfgang Denk
Dear Peter Tyser, In message <1284331129-12911-1-git-send-email-pty...@xes-inc.com> you wrote: > Using -fno-toplevel-reorder causes gcc to not reorder functions. This > ensures that an application's entry point will be the first function in > the application's source file. > > This change, along

Re: [U-Boot] [PATCH] examples/standalone: Use gcc's -fno-toplevel-reorder

2010-09-16 Thread Detlev Zundel
Hi Peter, > I agree we should be using main() as the entry point either way. I'll > add that to the TODO list. If we did go with -fno-toplevel-reorder I > could add the following to each application to make it clear what's > going on: > /* Define main() protoype first to ensure its the first fun

Re: [U-Boot] [PATCH] examples/standalone: Use gcc's -fno-toplevel-reorder

2010-09-12 Thread Peter Tyser
Hi Andrew, On Sun, 2010-09-12 at 21:00 -0500, Andrew Dyer wrote: > On Sun, Sep 12, 2010 at 17:38, Peter Tyser wrote: > > Using -fno-toplevel-reorder causes gcc to not reorder functions. This > > ensures that an application's entry point will be the first function in > > the application's source

Re: [U-Boot] [PATCH] examples/standalone: Use gcc's -fno-toplevel-reorder

2010-09-12 Thread Andrew Dyer
On Sun, Sep 12, 2010 at 17:38, Peter Tyser wrote: > Using -fno-toplevel-reorder causes gcc to not reorder functions.  This > ensures that an application's entry point will be the first function in > the application's source file. > > This change, along with commit 620bbba524fbaa26971a5004793010b16

[U-Boot] [PATCH] examples/standalone: Use gcc's -fno-toplevel-reorder

2010-09-12 Thread Peter Tyser
Using -fno-toplevel-reorder causes gcc to not reorder functions. This ensures that an application's entry point will be the first function in the application's source file. This change, along with commit 620bbba524fbaa26971a5004793010b169824f1b should cause a standalone application's entry point