public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Richard Henderson <rth@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: Aliases ...
Date: Sun, 30 Jan 2005 10:36:00 -0000	[thread overview]
Message-ID: <m3brb7yzj6.fsf@gromit.moeb> (raw)
In-Reply-To: <m3is6074yc.fsf@gromit.moeb> (Andreas Jaeger's message of "Fri, 14 Jan 2005 10:08:59 +0100")

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]


I still see these warnings and would like to help getting them fixed.

Richard, what do you suggest is the best thing to do?

Andreas

Andreas Jaeger <aj@suse.de> writes:

> Let's look closer at one example:
> ../sysdeps/ieee754/dbl-64/s_isinf.c:29: warning: ‘isinf’ aliased to undefined symbol ‘__isinf’
>
> The function is:
>
> int
> __isinf (double x)
> {
> 	int32_t hx,lx;
> 	EXTRACT_WORDS(hx,lx,x);
> 	lx |= (hx & 0x7fffffff) ^ 0x7ff00000;
> 	lx |= -lx;
> 	return ~(lx >> 31) & (hx >> 30);
> }
> hidden_def (__isinf)
> weak_alias (__isinf, isinf)
>
> And the warning appears for the weak_alias.  If I change it to:
> weak_alias (__GI___isinf, isinf)
>
> Everything is fine.
>
> so, is this the right way to do - and should we add a new macro, e.g.
> hidden_weak_alias to use in place of weak_alias above?
>
> Or how should this be solved to make GCC happy - and be convenienent
> for glibc?
>
> Andreas

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2005-01-30 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 21:00 Aliases Andreas Jaeger
     [not found] ` <20050109232721.GA23478@redhat.com>
2005-01-10  6:11   ` Aliases Andreas Jaeger
2005-01-14  9:09     ` Aliases Andreas Jaeger
2005-01-30 10:36       ` Andreas Jaeger [this message]
2005-01-14  8:54   ` Aliases Andreas Jaeger
2005-01-14 16:41     ` Aliases Roland McGrath
2005-01-14 18:41       ` Aliases Andreas Jaeger
2005-01-14 18:56         ` Aliases Roland McGrath
2005-01-10 17:14 ` Aliases H. J. Lu
2005-01-10 17:27   ` Aliases H. J. Lu
     [not found] <20050114192642.GC19955@redhat.com>
2005-01-14 19:30 ` Aliases Roland McGrath
2005-01-14 20:04   ` Aliases Jakub Jelinek
2005-01-15  7:19     ` Aliases Andreas Jaeger
2005-01-15  9:35       ` Aliases Jakub Jelinek
2005-01-15  9:49         ` Aliases Andreas Jaeger
2005-01-14 20:23   ` Aliases Andreas Schwab

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=m3brb7yzj6.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=libc-hacker@sources.redhat.com \
    --cc=rth@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).