Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   C++ (http://www.velocityreviews.com/forums/f39-c.html)
-   -   porting to 64 bit (http://www.velocityreviews.com/forums/t459803-porting-to-64-bit.html)

nprashanth@gmail.com 01-13-2007 05:02 AM

porting to 64 bit
 
Hi,

I've to port some code to a 64 bit platform (RedHat AS4). I was looking
for some compiler switches which can flag errors like this:

bash-3.00$ cat test.cpp
#include <string>

int main()
{
//unsigned long int being assigned to an unsigned int
unsigned xyz = std::string("").find("A");
}

I used some options, but they do not seem to flag the error:
bash-3.00$ g++ -c -Wconversion -Wimplicit -Wall -Wextra -m64 test.cpp
test.cpp: In function `int main()':
test.cpp:7: warning: unused variable 'xyz'

version: gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)

Are there any options which can flag such errors? If no, is there any
way to find such errors?

Thanks for your time,
Prashanth.


noone 01-13-2007 05:07 AM

Re: porting to 64 bit
 
On Fri, 12 Jan 2007 21:02:43 -0800, nprashanth wrote:

> Hi,
>
> I've to port some code to a 64 bit platform (RedHat AS4). I was looking
> for some compiler switches which can flag errors like this:
>
> bash-3.00$ cat test.cpp
> #include <string>



better to look for your answer in the gnu gcc forums



Ondra Holub 01-13-2007 03:42 PM

Re: porting to 64 bit
 

nprasha...@gmail.com napsal:
> Hi,
>
> I've to port some code to a 64 bit platform (RedHat AS4). I was looking
> for some compiler switches which can flag errors like this:
>
> bash-3.00$ cat test.cpp
> #include <string>
>
> int main()
> {
> //unsigned long int being assigned to an unsigned int
> unsigned xyz = std::string("").find("A");
> }
>
> I used some options, but they do not seem to flag the error:
> bash-3.00$ g++ -c -Wconversion -Wimplicit -Wall -Wextra -m64 test.cpp
> test.cpp: In function `int main()':
> test.cpp:7: warning: unused variable 'xyz'
>
> version: gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)
>
> Are there any options which can flag such errors? If no, is there any
> way to find such errors?
>
> Thanks for your time,
> Prashanth.


In any project is good approach to:
- turn on all warnings
- make code review (by other people who are not authors of code)
- use tools like valgrind or lint to check the code



All times are GMT. The time now is 10:32 PM.

Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.