https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68605
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
There's no need for the option you suggest.
You can use the 'specs' files that come with libgloss to write your own custom
rules for your board. For example, the arm rdimon specs file contains:
# rdimon.specs
#
# Spec file for AArch64 baremetal newlib with version 2 of the
# AngelAPI semi-hosting using the SVC trap instruction.
#
# This version supports extensibility through an extension mechanism.
%rename link_gcc_c_sequence rdimon_link_gcc_c_sequence
*rdimon_libc:
%{!specs=nano.specs:-lc} %{specs=nano.specs:-lc_nano}
*rdimon_libgloss:
%{!specs=nano.specs:-lrdimon} %{specs=nano.specs:-lrdimon_nano}
*link_gcc_c_sequence:
%(rdimon_link_gcc_c_sequence) --start-group %G %(rdimon_libc)
%(rdimon_libgloss) --end-group
*startfile:
crti%O%s crtbegin%O%s %{!pg:rdimon-crt0%O%s} %{pg:rdimon-crt0%O%s}
and you could customize this to do something suitable for your board.
