Sanjiv Kumar Gupta wrote:
> > What is stopping the value of 'foo' itself being > 255?
> Programmer will get an overflow error for that during linking.
For my curiosity, what's the background here? Do you really only have 256
bytes of storage on this system?
If you've got eight bit registers in a
Ivan Leo Puoti wrote:
> I would like to know if the FASTCALL calling convention will be
> supported by gcc on linux sometime soon, I need this for some
> software I'm writing.
It already is:
http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Function-Attributes.html
e.g.
int __attribute((fast
Just as another idea -
Steven Bosscher wrote:
> (The proper solution is of course to have an IR that we can stream
> to disk, *sigh* ;-)
AFAICT, MSVC solves this by generating some of the code when it reaches some
memory limit. So when GCC is under some memory pressure it could identify
functio
Ian Lance Taylor wrote:
> According to the PR, the bug is fixed in 4.1. You are testing a
> gcc-4.0 snapshot. Try testing a gcc-4.1 snapshot.
Then he's saying this is still a regression in gcc-4.0?
Nicola Musatti wrote:
> _main PROC
>
> ; 12 : char * b = "0123456789";
> ; 13 : for ( int l = 0; l < 1 << 30; ++l )
> ; 14 : f(b, l);
> ; 15 : }
>
> xor eax, eax
> ret 0
> _main ENDP
Note that it optimised away your whole program! It could blank
Andrew Haley wrote:
> > In this case, it's the Mac OS X man page. Which I now see doesn't
> > say the same thing as POSIX. Which was just the point I was
> > trying to make you can't rely on the return value for determining
> > the number of characters written.
> Yes we can. gcc is written in ISO
> Documentation error? They've got the same man page for printf(1)
> and printf(3):
Oh, except trying it on a real Mac they don't - that website's broken.
Simon, you need to type:
man 3 printf
to read about printf() the C function.
Rup.
__
Dennis Clarke wrote:
>Is there a way to allow the testsuite to just run regardless of
>how long it takes?
I think you need to pass "set timeout -1" into dejagnu. I'd suggest a larger
positive timeout instead.
I forget the correct way to do this - I used to end up editing the .exp files
