title: va_list initialization in different architecture
body: <pre><code>  va_list args = 0;
  </code></pre>
  
  <p>I found a code in my application as above, and it is compiling properly  in following gcc version.</p>
  
  <pre><code>~ $ /usr/sfw/bin/gcc -v
  Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
  Configured with: /sfw10/builds/build/sfw10-patch/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/ccs/
  bin/as --without-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
  Thread model: posix
  gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
  </code></pre>
  
  <p>But when i compiled the same code in new machine, it is giving issue since the va_list args is initialized with zero. Hope va_list is typedef of something and i removed the initialization of va_list with zero and it is compiled fine in new machine.</p>
  
  <p>But fortunately both old and new machine has same gcc version.</p>
  
  <pre><code>    NEW MACHINE GCC VERSION:
      Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs
  Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
  Thread model: posix
  gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
  </code></pre>
  
  <p>But i noticed that architecture of two machine is different. Is that causing any issue.</p>
  
  <p>Since stdarg is an standard library. So why it is varying based on architecture?</p>