Databases
StackOverflow2013
Postsdbo
POPorting C source code written for 32 to 64 bit
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPorting C source code written for 32 to 64 bit
    primarykey
    data
    text
    <p>The C source codes that I am trying to port into 64 bit runs without any warning in the 32 bit environment. When I compile in 64 bit Linux environment with the compile gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1, it shows the following warning mostly:</p> <pre><code>warning: cast to pointer from integer of different size </code></pre> <p>The above warning were the most. I used <strong>uintptr_t</strong> type and most of those warnings were removed. I could change the type <strong>int /unsigned int</strong> into 64 bit favorable using <strong>uintptr_t</strong>. But how can I change the following type to make compatible to 64 bit:</p> <pre><code>typedef void* POINTER; </code></pre> <p>I have changed the following code:</p> <pre><code>typedef unsigned int ABC; </code></pre> <p>into </p> <pre><code>typedef uintptr_t ABC </code></pre> <p>I got following warnings:</p> <pre><code>warning: passing argument 2 of ‘function’ from incompatible pointer type note: expected ‘ABC *’ but argument is of type ‘unsigned int *’ </code></pre> <p>Moreover, after changing type def into uintptr_t which were earlier either int or unsigned int, I am encountering most of the warnings as follows:</p> <pre><code>warning: inlining failed in call to ‘abc_StringCopy’: call is unlikely and code size would grow </code></pre> <p>The function tptp_StringCopy is as follows:</p> <pre><code>static __inline__ char* abc_StringCopy(void) { char *copy; copy = (char*)Malloc(yyleng+1); strcpy(copy, yytext); return copy; </code></pre> <p>How can I get rid of these warnings?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBenjamin
    1. USthetna
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPorting C source code written for 32 to 64 bit
      1. USChris Dennett
      1. VTFavorite
    2. VO
      singulars
      1. POPorting C source code written for 32 to 64 bit
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPorting C source code written for 32 to 64 bit
      1. This table or related slice is empty.
      1. VTUpMod
    1. COgcc 4.3.3 on 64 bit Slackware says unsigned long int is 8 bytes, which is equal to size of pointers.
      singulars
      1. POPorting C source code written for 32 to 64 bit
      1. USArthur Kalliokoski
    2. COYou don't seem to understand the difference between a `int *` and an `int`. Simply eliminating compiler warnings will not get you through porting an application, you need a better understanding of C, so you can understand what you are doing.
      singulars
      1. POPorting C source code written for 32 to 64 bit
      1. USmctylr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload