Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Alexandr Andreev <andreev@niisi.msk.ru>
Cc: linux-mips@oss.sgi.com
Subject: Re: 3 questions about linux-2.4.18 and R3000
Date: Tue, 28 May 2002 10:15:55 -0700	[thread overview]
Message-ID: <3CF3BB4B.504@mvista.com> (raw)
In-Reply-To: 3CF2A17D.6050207@niisi.msk.ru

Alexandr Andreev wrote:

> Jun Sun wrote:
> 
>> I took a look of the arch_get_unmapped_area(),  and it looks fine to me.
>>
>> Can you try the following changes and let me know what happens?
>>
>> 1) change COLOUR_ALIGN
>> #define COLOUR_ALIGN(addr,pgoff)     addr
> 
> 
> OK, It works for me.
> 


That indicate the logic of function works.

So the problems might lie on something else:

1) some caller pass in non-zero addr but does not check the return addr and 
assume the addr remains the same.

2) given the reported toolchain, I will double-check to see if COLOUR_ALIGN() 
is compiled correctly.  It is mildly complex.


I would be also interested to know if removing filp condition would solve your 
problem.  Nobody has explained why this condition is needed for doing 
COLOUR_ALIGN().


>>
>> We have been using gcc 2.9.5 and binutils 2.10.x for R3000 CPUs for 
>> quite a  while with no problems.  It seems newer gcc and binutiles are 
>> fine too.
>>
> I understand, but is there any __official__ recommended versions of these
> utils? http://oss.sgi.com/mips/mips-howto.html is out-of-date :(
> 


Who are the "officiers" to decide on __official__ versions? :-)  If you are 
really uncomfortable with non-official stuff, you might want to consider 
paying some vendor and I am sure you will be given an "official" version.

Jun

  reply	other threads:[~2002-05-28 17:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24 22:16 3 questions about linux-2.4.18 and R3000 Alexandr Andreev
2002-05-24 21:10 ` Jun Sun
2002-05-27 21:13   ` Alexandr Andreev
2002-05-28 17:15     ` Jun Sun [this message]
2002-05-30  0:18       ` Alexandr Andreev
2002-05-31  9:43       ` Gleb O. Raiko
2002-06-03  8:55         ` Ralf Baechle
2002-06-03 18:30           ` Maciej W. Rozycki
2002-06-03 22:40             ` Ralf Baechle
2002-06-03 23:01               ` Thiemo Seufer
2002-06-03 23:04                 ` Ralf Baechle
2002-06-03 23:11                   ` Thiemo Seufer
2002-06-03 23:15                     ` Ralf Baechle
2002-06-03 23:53                       ` Thiemo Seufer
2002-06-04 17:41                         ` nick
2002-06-05 22:37                           ` Thiemo Seufer
2002-06-05 23:50                             ` Ilya Volynets
2002-06-06 23:54                               ` Thiemo Seufer
2002-06-04 14:39                   ` Maciej W. Rozycki
2002-06-04 14:37                 ` Maciej W. Rozycki
2002-06-05 22:38                   ` Thiemo Seufer
2002-06-04 14:34               ` Maciej W. Rozycki
2002-06-04 11:31           ` Gleb O. Raiko

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=3CF3BB4B.504@mvista.com \
    --to=jsun@mvista.com \
    --cc=andreev@niisi.msk.ru \
    --cc=linux-mips@oss.sgi.com \
    /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