other/2003: libgcc ABI

[Joseph Myers]

>Number:         2003
>Category:       other
>Synopsis:       libgcc ABI
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 15 16:56:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        2.97 20010211 (experimental)
>Organization:
none
>Environment:
System: Linux decomino 2.2.18 #1 Sun Jan 7 21:04:55 UTC 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:

libgcc-std.ver includes:

  # ??? Some of these are for `-a', which ought to die.
  __bb
  __bb_exit_func
  __bb_fork_func
  __bb_init_func
  __bb_init_trace_func
  __bb_trace_func
  __bb_trace_ret

  # ??? Symbols that perhaps unused should be nuked.
  __builtin_saveregs
  __clear_cache
  __dummy
  __empty
  __eprintf
  __gcc_bcmp

If these symbols appear in a released shared libgcc, we need to
support them as part of the libgcc ABI for ever.  Thus, we must
resolve, before GCC 3.0 is released, whether each of these symbols
should be part of the libgcc ABI or not.

>How-To-Repeat:

Want to get rid of one of these symbols after GCC 3.0 but be unable to
since it's been fixed in the ABI.

>Fix:

Identify the purpose of each symbol listed above, and either document
it or remove it.
>Release-Note:
>Audit-Trail:
>Unformatted: