From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Matheus Almeida <Matheus.Almeida@imgtec.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>,
Doug Gilmore <Doug.Gilmore@imgtec.com>
Subject: Re: [Patch, mips]: Add support for FR=1/o32. Update implemention of setjmp/longjmp
Date: Sat, 30 Nov 2013 08:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1311261632530.25885@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1311261609530.25885@digraph.polyomino.org.uk>
On Tue, 26 Nov 2013, Joseph S. Myers wrote:
> incompatibilities should be detected by the dynamic linker, not "need to
> be recompiled". I suggest looking at Maciej's NaN changes as a model.
Sorry, I see your "need to be recompiled" was about old -mfp64 binaries,
which indeed we don't need to care about. But we *do* need to ensure
incompatibilities between o32-fp32 and o32-fp64 binaries / shared
libraries are detected, which means doing similar things to Maciej's patch
to check ELF flags, distinguish libraries in ldconfig and arguably use a
different dynamic linker name (or two such names, if o32-fp64 is supported
with both NaN variants). (New dynamic linker names mean changes to specs
in GCC, but those changes should be small and so fine even in development
stage 3.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-11-26 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 11:34 Matheus Almeida
2013-11-26 16:25 ` Joseph S. Myers
2013-11-30 8:03 ` Joseph S. Myers [this message]
2013-12-04 2:45 ` Doug Gilmore
2013-12-04 14:56 ` Joseph S. Myers
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=Pine.LNX.4.64.1311261632530.25885@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Doug.Gilmore@imgtec.com \
--cc=Matheus.Almeida@imgtec.com \
--cc=libc-ports@sourceware.org \
/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).