From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Kill __errno_location PLT slot in --with-tls --with-__thread build
Date: Fri, 15 Nov 2002 14:46:00 -0000 [thread overview]
Message-ID: <200211152246.gAFMknn10680@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Friday, 15 November 2002 20:58:13 +0100 <20021115205813.M6569@sunsite.ms.mff.cuni.cz>
In your changes, on ia64 now there will be no ldexp{,f,l} in libm at all.
Was that the plan? I think that will break versioned dependencies.
I did some pure makefile hackery to generate the m_foo.? source files (two
more rules per dir in sysd-rules) that dtrt for .c vs .S generically. It
needs nothing in sysdeps, and won't require any more files anywhere if we
need to do the same for another of those modules.
next prev parent reply other threads:[~2002-11-15 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 11:58 Jakub Jelinek
2002-11-15 12:29 ` Roland McGrath
2002-11-15 13:06 ` Roland McGrath
2002-11-15 14:46 ` Roland McGrath [this message]
[not found] <20021115161220.I27455@devserv.devel.redhat.com>
2002-11-15 13:17 ` Roland McGrath
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=200211152246.gAFMknn10680@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@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).