public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Get rid of __libm_error_support PLT entry on IA-64
Date: Fri, 23 Apr 2004 13:36:00 -0000	[thread overview]
Message-ID: <20040423112430.GL5191@sunsite.ms.mff.cuni.cz> (raw)

Hi!

2004-04-23  Jakub Jelinek  <jakub@redhat.com>

	* sysdeps/ia64/fpu/libm_support.h (__libm_error_support): Add
	libc_hidden_proto.  Define to __GI___libm_error_support for
	assembly going into libc.so.
	* sysdeps/ia64/fpu/libc_libm_error.c (__libm_error_support): Add
	libc_hidden_def.

--- libc/sysdeps/ia64/fpu/libm_support.h.jj	2004-04-21 19:00:15.000000000 -0400
+++ libc/sysdeps/ia64/fpu/libm_support.h	2004-04-23 09:20:11.000000000 -0400
@@ -239,6 +239,7 @@ typedef enum
 } error_types;
 
 void __libm_error_support(void*,void*,void*,error_types);
+libc_hidden_proto(__libm_error_support)
 
 #define BIAS_64  1023
 #define EXPINF_64  2047
@@ -340,6 +341,13 @@ extern _LIB_VERSION_TYPE _LIB_VERSION;
 // This is a run-time variable and may effect
 // floating point behavior of the libm functions
 
+#elif defined _LIBC
+
+# if !defined NOT_IN_libc && defined SHARED && defined DO_VERSIONING \
+     && !defined HAVE_BROKEN_ALIAS_ATTRIBUTE && !defined NO_HIDDEN
+#  define __libm_error_support  __GI___libm_error_support
+# endif
+
 #endif	/* __ASSEMBLER__ */
 
 /* Support for compatible assembler handling.  */
--- libc/sysdeps/ia64/fpu/libc_libm_error.c.jj	2001-02-19 17:08:30.000000000 -0500
+++ libc/sysdeps/ia64/fpu/libc_libm_error.c	2004-04-23 09:16:00.000000000 -0400
@@ -11,3 +11,4 @@ __libm_error_support (void *arg1, void *
 {
   __set_errno (ERANGE);
 }
+libc_hidden_def (__libm_error_support)

	Jakub

             reply	other threads:[~2004-04-23 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 13:36 Jakub Jelinek [this message]
2004-05-03 22:41 ` Ulrich Drepper

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=20040423112430.GL5191@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.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).