Richard Kenner wrote:
A few comments:
Many portable C programs assume that signed integer overflow wraps around
reliably using two's complement arithmetic.
I'd replace "portable C programs" with "widely-used C programs". The normal
use of "portable" means that it conforms to the standard.
Paul Eggert wrote:
Andrew Pinski <[EMAIL PROTECTED]> writes:
Let me make the point that signed overflow has been undefined since
before the C standard was finialized and in fact there is a nice
paper/book called "C Traps and Pitfalls[2]" which mentions all of this
back in 1988.
C Traps and Pi
E. Weddington wrote:
Michael N. Moran wrote:
Robert Dewar wrote:
But there must be a way to write stuff into the instruction data
space, or how would you load code? So you just have to setup an
auxiliary stack in code space.
The AVR is an embedded processor, and the instruction space is
is Flash *
Stefan Strasser wrote:
Mike Stump schrieb:
On Friday, April 1, 2005, at 08:48 AM, Stefan Strasser wrote:
if gcc uses more memory than physically available it spends a _very_
long time swapping
Swapping, what's that? Here's $20, go buy a gigabyte.
expect memory to become a problem again with the
Florian Weimer wrote:
* Ranjit Mathew:
Without looking at the patent, I would hazard the guess
that it is about Win32 Structured Exception Handling (SEH):
http://www.microsoft.com/msj/0197/exception/exception.aspx
(The linked-to mail from the GCC mailing list seems to
confirm this.)
Indeed. Expli
Ron Hudson wrote:
Hi,
I am teaching myself C by writing programs. I have some questions about
proper practices...
Ask in news:comp.lang.c
Robert Dewar wrote:
Scott Robert Ladd wrote:
To support different expectations, I suggest defining the following
floating-point options for GCC. This is a conceptual overview; once
there's a consensus the categories, I'll propose something more formal.
-ffp-correct
This option focuses code ge
Robert Dewar wrote:
Scott Robert Ladd wrote:
To support different expectations, I suggest defining the following
floating-point options for GCC. This is a conceptual overview; once
there's a consensus the categories, I'll propose something more formal.
-ffp-correct
This option focuses code ge
Robert Dewar wrote:
Russell Shaw wrote:
The original bug was about testing the equality of doubles. I think
that's
just plain mathematically bad. Error bands should be used to test for
"equality", using a band that is in accordance with the minimum precision
specified
Shaun Jackman wrote:
Hello,
I'm implementing a tiny vfork/exit implementation using setjmp and
longjmp. Since the function calling setjmp can't return (if you still
want to longjmp to its jmp_buf) I implemented vfork using a statement
expression macro. Here's my implementation of vfork.
jmp_buf
Stephen Torri wrote:
I am interested in reading the actual grammar files used for parsing C
and C++ programming languages inside gcc. Where are these files located?
Stephen
gcc-3.4.3/gcc/c-parse.in
gcc-3.4.3/gcc/c-parse.y
Joseph S. Myers wrote:
On Mon, 11 Jul 2005, Michael Cieslinski wrote:
I also could convert parts of the ggcinternals manual into wiki pages.
But only if there is a consensus about this being the way to go.
I'm sure it's the wrong way to go. I find a properly formatted and
indexed book far m
How do i disable that? My code explicitly compares string pointers.
13 matches
Mail list logo