Subject:
|
Warning cleanup questions with gcc3.2
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Thu, 5 Sep 2002 20:29:48 GMT
|
Viewed:
|
2142 times
|
| |
| |
When compiling brickos with gcc3.2, I get a lot (about 360 or so) of
warnings about two things;
a) warning: multi-line string literals are deprecated
These seem to be mostly quotes around blocks of assembly code. Some of
the code in lib/mint seems to compile just fine and is in the form of;
__asm__ (
".section .text\n\t"
".global ___divhi3\n"
"___divhi3:\n\t"
"push r5\n\t"
"push r6\n\t"
"mov.w r0,r6\n\t"
"mov.w r1,r5\n\t"
"jsr @@82\n\t"
"mov.w r6,r0\n\t"
"pop r6\n\t"
"pop r5\n\t"
"rts"
);
Note the quotes around each line. I think moving to this convention is
the right thing to do.
b) warning: const qualifier ignored on asm
These seem to be due to things like this;
#define bit_set(byte,bit) \
__asm__ ASMCONST ( "bset %0,@%1\n" : : "i" (bit),"r" (byte))
I believe the right thing to do here is to remove the "ASMCONST".
So the questions I have are; Are these backward compatible solutions? Are
they good solutions? Should I spend the time to whip up a patch that will
touch a lot of files...
J*
|
|
Message has 2 Replies: | | Re: Warning cleanup questions with gcc3.2
|
| (...) I am running 3.1 and got the same error. But for user programs only because a line in boot/config.h is too long. In fact this is no error but just a warning. Looks bad but the code is ok. (...) If you look at the beginning of the file (I think (...) (22 years ago, 5-Sep-02, to lugnet.robotics.rcx.legos)
| | | Re: Warning cleanup questions with gcc3.2
|
| (...) <snip> (...) I'd like to say not at this time. Let me explain and then let's all comment so I can see how my idea resonates with ya'll ;-) I'd like to hold off addressing the GCC 3.x issues for only this upcoming release (brickOS 1.0.0). My (...) (22 years ago, 6-Sep-02, to lugnet.robotics.rcx.legos)
|
5 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|