Subject:
|
Re: memcpy patch for gcc 2.95.2 wanted
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Sun, 26 Mar 2000 02:18:22 GMT
|
Viewed:
|
2348 times
|
| |
|
|
In lugnet.robotics.rcx.legos, Rossz Vámos-Wentworth writes:
> In an attempt to track down my RCX lockup problems I've been rereading
> the older messages and came across the discussion that sounded exactly
> like my problem: the RCX locks up when dll is executed. The conclusion
> was that bad code was generated for the memcpy function, but I didn't
> see a solution posted.
That was probably me. I don't know anything about GCC asm macros so I wasn't
sure if it was a bug in memcpy or a bug in GCC's code generation. I solved the
problem by going to egcs-1.1.2 which generates correct code. I was hoping that
someone else would take it from there!
--Ben
|
|
Message has 1 Reply:
 | | Re: memcpy patch for gcc 2.95.2 wanted
|
| (...) Sorry... I was going to recommend the same thing last night, but got sidetracked (it has been a tough two days to be a Duke basketball fan.) I have a question: from where in the code is the incorrect assembly generated? i.e., could it be (...) (25 years ago, 26-Mar-00, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | memcpy patch for gcc 2.95.2 wanted
|
| In an attempt to track down my RCX lockup problems I've been rereading the older messages and came across the discussion that sounded exactly like my problem: the RCX locks up when dll is executed. The conclusion was that bad code was generated for (...) (25 years ago, 24-Mar-00, to lugnet.robotics.rcx.legos)
|
11 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
