From: Matthew Locke <mlocke@mvista.com>
To: Denton Gentry <denny@dominetsystems.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: glibc 2.2.x?
Date: Tue, 15 May 2001 12:24:22 -0700 [thread overview]
Message-ID: <3B018266.49F9E6CB@mvista.com> (raw)
In-Reply-To: 3B017F0B.B89B3A94@dominetsystems.com
The problem we ran into with 2.2.2 was the optimized memset wasn't
aligned properly. We reverted back to the generic memset and haven't
had any trouble on 8xx. I am not aware of any similar issues on the 405,
but...
Denton Gentry wrote:
>
> About 6 weeks ago there were a couple messages on the list
> about glibc 2.2.x and embedded PowerPC. Has anyone made more
> progress?
> I'm trying to use glibc2.2.3 on a Walnut board, and cannot
> start any processes. The MVista glibc-2.1.3 and ld.so.1 work
> fine on this platform. My problem with glibc 2.2.3 looks similar
> to the problems described a few weeks ago (fault when linking
> libraries).
>
> Just for reference, heres what I did to glibc 2.2.3:
>
> I had to move sysdeps/powerpc/fclrexcept.c to the fpu subdirectory,
> as it deals with the FPU (sysdeps/generic/fclrexcept.c will be used
> instead). I also had to remove the fenv_const and fe_nomask references
> from the Makefile.
> So far as I can see __elf_machine_runtime_setup() in
> sysdeps/powerpc/dl-machine.c has been updated to know that
> not all PPCs have 32 byte cache lines, so I left it alone.
> memset.S does still have an assumption about cache line
> size ("subfic rALIGN, rALIGN, 0x20"), so I moved it aside
> to let the generic version be used.
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-05-15 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 19:10 glibc 2.2.x? Denton Gentry
2001-05-15 19:24 ` Matthew Locke [this message]
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=3B018266.49F9E6CB@mvista.com \
--to=mlocke@mvista.com \
--cc=denny@dominetsystems.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).