This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] powerpc64 config pass 3


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Jacobowitz wrote:

This isn't right.  Let's try again: The only reason to put something
under powerpc32/ is if it is more appropriate for there to be _no_
implementation on powerpc64.  I assume powerpc64 supports __longjmp, so
you should just be creating sysdeps/powerpc/powerpc64/__longjmp.S.
No. Files are to be moved into powerpc32 if the files will never be used on powerpc64. So, if there is a powerpc64 directory which has a copy and there will be no other PPC architectures which is like powerpc32 but sufficiently different to not be placed under powerpc32, then the files should remain in powerpc. I cannot see this happening at all so moving the files is OK.

- -- - ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9cW+Q2ijCOnn/RHQRAhBEAJ9hipUH1Uv0VDdrWbXJ77fGDb9fKgCfQtBE
NJCBmsuD+gmFvNZQZkSI/Bc=
=E4OA
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]