Arm Community
Site
Search
User
Site
Search
User
Arm Developer
Documentation
Learning Paths
On-Demand Videos
Groups
Arm Ambassadors
Education Hub
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Automotive forum
Compilers and Libraries forum
Embedded and Microcontrollers forum
Internet of Things (IoT) forum
Keil forum
Laptops and Desktops forum
Mobile, Graphics, and Gaming forum
Morello forum
Operating Systems forum
Servers and Cloud Computing forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI blog
Announcements
Architectures and Processors blog
Automotive blog
Embedded and Microcontrollers blog
Internet of Things (IoT) blog
Laptops and Desktops blog
Mobile, Graphics, and Gaming blog
Operating Systems blog
Servers and Cloud Computing blog
SoC Design and Simulation blog
Tools, Software and IDEs blog
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Arm Development Studio forum
Building Linux applications/libs in GCC emulation mode
Jump...
Cancel
Locked
Locked
Replies
5 replies
Subscribers
120 subscribers
Views
3929 views
Users
0 members are here
Options
Share
More actions
Cancel
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Building Linux applications/libs in GCC emulation mode
Marius Cetateanu
over 11 years ago
Parents
Edmund Player
over 11 years ago
Note: This was originally posted on 2nd June 2011 at
http://forums.arm.com
[font=arial, verdana, tahoma, sans-serif][size=2]I have played around with this... it doesn't look like armcc translates any of the -Wxyz warning options from gcc (except -Wall). But, it seems to handle -f* options where its has equivalentsI think that warning L6238E is harmless in almost all cases; it is given by armlink because libgcc and other GCC/GNU assembler-built libraries don't contain ARM build attributes for marking that 8-byte stack alignment is required/preserved. You could just suppress this globally by setting ARMCC50_LINKOPT="--diag_suppress=6238". Warning L6439W is again harmless; it'll most likely be generated for out-of-line copies of inline functions in Comdat groups, where GCC hasn't strictly followed ELF rules about the groups and therefore armlink is rejecting that copy and instead using a copy from the same Comdat group that was generated in one of the armcc-compiled object files.Updating to the latest GNU toolchain is also worth a punt.
[/size][/font]
Cancel
Vote up
0
Vote down
Cancel
Reply
Edmund Player
over 11 years ago
Note: This was originally posted on 2nd June 2011 at
http://forums.arm.com
[font=arial, verdana, tahoma, sans-serif][size=2]I have played around with this... it doesn't look like armcc translates any of the -Wxyz warning options from gcc (except -Wall). But, it seems to handle -f* options where its has equivalentsI think that warning L6238E is harmless in almost all cases; it is given by armlink because libgcc and other GCC/GNU assembler-built libraries don't contain ARM build attributes for marking that 8-byte stack alignment is required/preserved. You could just suppress this globally by setting ARMCC50_LINKOPT="--diag_suppress=6238". Warning L6439W is again harmless; it'll most likely be generated for out-of-line copies of inline functions in Comdat groups, where GCC hasn't strictly followed ELF rules about the groups and therefore armlink is rejecting that copy and instead using a copy from the same Comdat group that was generated in one of the armcc-compiled object files.Updating to the latest GNU toolchain is also worth a punt.
[/size][/font]
Cancel
Vote up
0
Vote down
Cancel
Children
No data