Electronics & Programming

develissimo

Open Source electronics development and programming

  • You are not logged in.
  • Root
  • » MSPGCC
  • » [Mspgcc-users] what happened to __get_frame_address? [RSS Feed]

#1 Jan. 28, 2011 20:01:55

Alex S.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[Mspgcc-users] what happened to __get_frame_address?


Hi all!

I am trying to make a switch to mspgcc4 but I get an `undefined
reference to `__get_frame_address' ' error from the linker (in gcc 3..
the macro I am using, GET_FRAME_ADDR_F( __FUNCTION__ ), expands to
assembly code so it does work). This should be a built-in, it seems
and the extern declaration in iomacros.h may be screwing it up. Is
there a fix for this(other functions of similar kind, like
__bic_sr_irq, work fine)?

The error is the same when I use the latest git version of mspgcc4.

Finally, unrelated to this, the code that mspgcc4 generates is about
1K longer than the 3.2.3 branch. Is there a trick (I know this
question is too general but I am looking for something obvious I may
have overlooked) other than -Os switch to make it generate smaller
code?

Alex


Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/mspgcc-users

Offline

#2 Jan. 30, 2011 20:43:24

Peter B.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[Mspgcc-users] what happened to __get_frame_address?


It appears that built-in is not recognized as a built-in, unlike
__bic_sr_irq which is declared in the same place. I don't know why offhand;
sorry I had to get the 20110130 release out today to meet somebody's
deadline and didn't have time to look at this first. Would you please
create a tracker ticket for this issue on the sourceforge bugs page? I'm
not sure when I'll get to it, but hopefully it'll be within the next couple
weeks.

Code size variation between different versions of gcc can be fairly large,
and I'm not convinced -Os always does the best thing. I am aware of one
problem documented athttps://sourceforge.net/tracker/?func=detail&aid=3152588&group_id=42303&atid=432701thathas a significant effect on some versions. Although I marked that
closed because I found an adequate workaround, in fact the memmov*
instructions should still be implemented, and if I get an opportunity I'll
do that.

Peter

On Fri, Jan 28, 2011 at 1:59 PM, Alex Shibakov <alex***@*mail.com> wrote:

> Hi all!
>
> I am trying to make a switch to mspgcc4 but I get an `undefined
> reference to `__get_frame_address' ' error from the linker (in gcc 3..
> the macro I am using, GET_FRAME_ADDR_F( __FUNCTION__ ), expands to
> assembly code so it does work). This should be a built-in, it seems
> and the extern declaration in iomacros.h may be screwing it up. Is
> there a fix for this(other functions of similar kind, like
> __bic_sr_irq, work fine)?
>
> The error is the same when I use the latest git version of mspgcc4.
>
> Finally, unrelated to this, the code that mspgcc4 generates is about
> 1K longer than the 3.2.3 branch. Is there a trick (I know this
> question is too general but I am looking for something obvious I may
> have overlooked) other than -Os switch to make it generate smaller
> code?
>
> Alex
>
>
>
> Mspgcc-users mailing list
> Mspgcc-us***@*ists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/mspgcc-users>
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/mspgcc-users

Offline

  • Root
  • » MSPGCC
  • » [Mspgcc-users] what happened to __get_frame_address? [RSS Feed]

Board footer

Moderator control

Enjoy the 15th of December
PoweredBy

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support