* Why does GCC(libgcc) pack libgcc_eh.a into libgcc.a in baremetal ?
[not found] <7fea0954-2d74-4014-9684-b39598b8ec60@Spark>
@ 2022-04-22 6:44 ` Jojo R
0 siblings, 0 replies; only message in thread
From: Jojo R @ 2022-04-22 6:44 UTC (permalink / raw)
To: GCC Development
Hi,
Are there some history or reason for this design ?
I think it’s clear & simple to keep coherent logic,
namely that there should be libgcc_eh.a for exceptions :)
Add Makefile.in segment of libgcc as following:
# Build LIB2ADDEH, LIB2ADDEHSTATIC, and LIB2ADDEHSHARED. If we don't have
# libgcc_eh.a, only LIB2ADDEH matters. If we do, only LIB2ADDEHSTATIC and
# LIB2ADDEHSHARED matter. (Usually all three are identical.)
c_flags := -fexceptions
ifeq ($(enable_shared),yes)
libgcc-eh-objects += $(addsuffix $(objext),$(basename $(notdir $(LIB2ADDEHSTATIC))))
libgcc-s-objects += $(addsuffix _s$(objext),$(basename $(notdir $(LIB2ADDEHSHARED))))
iter-items := $(sort $(LIB2ADDEHSTATIC) $(LIB2ADDEHSHARED))
include $(iterator)
else
# Not shared. LIB2ADDEH are added to libgcc.a.
libgcc-objects += $(addsuffix $(objext),$(basename $(notdir $(LIB2ADDEH))))
iter-items := $(LIB2ADDEH)
include $(iterator)
endif
— Jojo
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-04-22 6:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <7fea0954-2d74-4014-9684-b39598b8ec60@Spark>
2022-04-22 6:44 ` Why does GCC(libgcc) pack libgcc_eh.a into libgcc.a in baremetal ? Jojo R
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).