This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Thu, 24 Jun 1999, Jeffrey A Law wrote: > > You are saying here about machine code differences, and this is not what > > -mcpu=i486 is documented to do. > True, but I know people are using it the other way. That might be, but those people are wrong then. They are relaying on a undocumented feature - no, wait - the documentation says exactly the opposite of what they are using. So it is not even an undocumented feature. And it is a whole lot simpler to add -march=i486 where different machine code needs to be generated than to dig out the consequences of making that the default on a genuine i386. > > That would be great as well. Any chance of getting some of this fixed? > I can't do it right now. Maybe someone else can. Well, it should be a slighly modified version of rth's patch. But we have to agree on some sort of schema. I suggest to have the __i486 and __i486__ defines reserved for the -march=i486. For the -mcpu=i486 we could use something like __sched_i486__ or something like that. Other suggestions? Cristian -- ---------------------------------------------------------------------- Cristian Gafton -- gafton@redhat.com -- Red Hat, Inc. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ UNIX is user friendly. It's just selective about who its friends are.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |