public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lee Iverson <leei@ai.sri.com>
To: egcs@cygnus.com
Subject: Patches to Makefile.in for libgcc2 exceptions.
Date: Wed, 29 Oct 1997 09:50:00 -0000	[thread overview]
Message-ID: <199710291745.JAA11589@Canada.AI.SRI.COM> (raw)

I understand that a solution may have already been installed, but
perhaps for those completely paranoid about extra code/data size
generated by exceptions this would be a bit more palatable than simply
compiling the entire libgcc2.a with -fexceptions.

Are there any more functions which need to be exception ready?  Or
have I been too generous.  Maybe LIB2FUNCS_EH needs a little
refinement...

1997-10-29  Lee Iverson  <leei@Rapley.AI.SRI.COM>

	* Makefile.in (LIBGCC2_CFLAGS_EH): Add -fexceptions for certain
	functions in libgcc2 which need to be exception safe.
	(LIB2FUNCS_EH): Moved exception-sensitive functions from LIB2FUNCS.
	(libgcc2.a): Add loop through LIB2FUNCS_EH with LIBGCC2_CFLAGS_EH
	to ensure that exceptions will be handled properly.

*** gcc/Makefile.in.~1~	Fri Oct 24 14:58:24 1997
--- gcc/Makefile.in	Mon Oct 27 12:31:32 1997
*************** LIBGCC2 = libgcc2.a
*** 271,274 ****
--- 271,275 ----
  LIBGCC2_DEBUG_CFLAGS = -g1
  LIBGCC2_CFLAGS = -O2 $(LIBGCC2_INCLUDES) $(GCC_CFLAGS) $(TARGET_LIBGCC2_CFLAGS) $(LIBGCC2_DEBUG_CFLAGS) -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED @inhibit_libc@
+ LIBGCC2_CFLAGS_EH = -fexceptions $(LIBGCC2_CFLAGS)
  
  # Additional options to use when compiling libgcc2.a.
*************** LIB2FUNCS = _muldi3 _divdi3 _moddi3 _udi
*** 629,635 ****
      _fixxfdi _fixunsxfdi _floatdixf _fixunsxfsi \
      _fixtfdi _fixunstfdi _floatditf \
!     __gcc_bcmp _varargs __dummy _eprintf _op_new _op_vnew _new_handler \
!     _op_delete _op_vdel _bb _shtab _clear_cache _trampoline __main _exit \
!     _ctors _eh  _pure
  
  # The files that "belong" in CONFIG_H are deliberately omitted
--- 630,638 ----
      _fixxfdi _fixunsxfdi _floatdixf _fixunsxfsi \
      _fixtfdi _fixunstfdi _floatditf \
!     __gcc_bcmp _varargs __dummy _eprintf \
!     _bb _shtab _clear_cache _trampoline __main _exit
! 
! LIB2FUNCS_EH = _op_new _op_vnew _new_handler _op_delete _op_vdel \
!     _ctors _eh _pure
  
  # The files that "belong" in CONFIG_H are deliberately omitted
*************** libgcc2.a: libgcc2.c libgcc2.ready $(CON
*** 966,969 ****
--- 969,981 ----
  	  echo $${name}; \
  	  $(GCC_FOR_TARGET) $(LIBGCC2_CFLAGS) $(INCLUDES) -c -DL$${name} \
+ 	      $(srcdir)/libgcc2.c -o $${name}$(objext); \
+ 	  if [ $$? -eq 0 ] ; then true; else exit 1; fi; \
+ 	  $(AR) $(AR_FLAGS) tmplibgcc2.a $${name}$(objext); \
+ 	  rm -f $${name}$(objext); \
+ 	done
+ 	for name in $(LIB2FUNCS_EH); \
+ 	do \
+ 	  echo $${name}; \
+ 	  $(GCC_FOR_TARGET) $(LIBGCC2_CFLAGS_EH) $(INCLUDES) -c -DL$${name} \
  	      $(srcdir)/libgcc2.c -o $${name}$(objext); \
  	  if [ $$? -eq 0 ] ; then true; else exit 1; fi; \

-------------------------------------------------------------------------------
Lee Iverson     		SRI International
leei@ai.sri.com			333 Ravenswood Ave., Menlo Park CA 94025
http://www.ai.sri.com/~leei/	(650) 859-3307

                 reply	other threads:[~1997-10-29  9:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199710291745.JAA11589@Canada.AI.SRI.COM \
    --to=leei@ai.sri.com \
    --cc=egcs@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).