[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnewsense-dev] binutils which works around loongson2f NOP bug by de
From: |
Karl Goetz |
Subject: |
Re: [Gnewsense-dev] binutils which works around loongson2f NOP bug by default |
Date: |
Sun, 11 Apr 2010 09:43:42 +0930 |
On Sat, 10 Apr 2010 10:26:46 -0400
Mark H Weaver <address@hidden> wrote:
> On Sat, Apr 10, 2010 at 08:55:00AM +0930, Karl Goetz wrote:
> > > One minor caveat, however: some bare (unfixed) NOPs are still
> > > included in the C run-time library which is normally statically
> > > linked into executables. I guess we need to recompile gcc using
> > > this version of binutils to take care of that issue.
> >
> > Rebuilding gcc will only help for statically compiled packages from
> > this point though, so it seems like a suitably low priority issue
> > there.
>
> No, I'm not talking about glibc. I'm talking about
>
> /lib/ld.so.1
> /usr/lib/crt*.o
> /usr/lib/gcc/mipsel-linux-gnu/4.3/crt*.o
>
> and maybe others, which get statically-linked to most executables,
> even "dynamically-linked" ones. Try "gcc -v -o foo foo.c" where foo.c
> is some simple self-contained program, and look at what's getting
> linked in. Try "objdump -d foo" and you'll see bare NOPs in the code
> that came from the aforementioned .o files.
>
> We'll need to rebuild gcc and glibc using the new binutils to take
> care of all of these issues, before rebuilding other packages.
Thanks for the clarification.
Is there a subset of packages which we should make a high priority for
rebuild? (eg, dozen packages which stop 90% of crashes)
- gcc
- binutils
- linux
others?
kk
--
Karl Goetz, (Kamping_Kaiser / VK5FOSS)
Debian contributor / gNewSense Maintainer
http://www.kgoetz.id.au
No, I won't join your social networking group
signature.asc
Description: PGP signature
Re: [Gnewsense-dev] binutils which works around loongson2f NOP bug by default, Karl Goetz, 2010/04/08