This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/47100] No prototype for âvxworks_override_options'
- From: "amylaar at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 30 Dec 2010 22:01:59 +0000
- Subject: [Bug target/47100] No prototype for âvxworks_override_options'
- Auto-submitted: auto-generated
- References: <bug-47100-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47100
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmitchel at gcc dot
| |gnu.org, nathan at
| |codesourcery dot com,
| |rsandifo at gcc dot gnu.org
--- Comment #1 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2010-12-30 22:01:52 UTC ---
Why do the *-wrs-vxworksae targets use vxworks.o at all? None of the
functions are used. It seems the easiest way to avoid the warnings
is not to build vxworks.o .
Or should is this difference between the VxWorks and VxWorks AE configurations
and error, and should the VXWORKS_OVERRIDE_OPTIONS / TARGET_ASM_CONSTRUCTOR /
TARGET_ASM_DESTRUCTOR definitions be moved to vx-common.h ?