avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-libc-dev] [bug #19050] gcrt1.S should call main rather thanjump


From: Eric Weddington
Subject: RE: [avr-libc-dev] [bug #19050] gcrt1.S should call main rather thanjumping to it
Date: Tue, 13 Feb 2007 11:55:23 -0700

 

> -----Original Message-----
> From: Anatoly Sokolov [mailto:address@hidden 
> Sent: Tuesday, February 13, 2007 11:32 AM
> To: Eric Weddington; 'Joerg Wunsch'; Joerg Wunsch; 
> address@hidden
> Subject: Re: [avr-libc-dev] [bug #19050] gcrt1.S should call 
> main rather thanjumping to it
> 
> ----- Original Message ----- 
> From: "Eric Weddington" <address@hidden>
> Sent: Tuesday, February 13, 2007 8:35 PM
> Subject: RE: [avr-libc-dev] [bug #19050] gcrt1.S should call 
> main rather
> thanjumping to it
> 
> >
> > You make some very good points. Unfortunately, main() is 
> already converted
> > over to a normal function in gcc 4.x. Do you propose that 
> we convert it 
> > back?
> 
> No. In oficial GCC 4.x main() do not converted to a normal function. 
> 'atmega256' patch does it.
> 
> > Can someone remember what was the reasoning behind making 
> main() a normal
> > function? Is the reason still valid?
> 
> Marek suggested to make  main() a normal function, for simplification 
> transitions to RTL prologues/epilogues:
> https://savannah.nongnu.org/task/?4355
> 
> I sent a patch to use RTL prologues/epilogues in GCC two 
> months ago. 'main' 
> function is processed separately, to be called with XJMP. 
> Marek reason do 
> not valid.

Ah! Thank you for making this clear.

Joerg, what do you think of this? Time to revisit the atmega256x patch?

Eric





reply via email to

[Prev in Thread] Current Thread [Next in Thread]