diff options
| author | Gerald Pfeifer <gerald@pfeifer.com> | 2024-07-07 22:01:40 +0200 |
|---|---|---|
| committer | Gerald Pfeifer <gerald@pfeifer.com> | 2024-07-07 22:01:40 +0200 |
| commit | a28046e215307cf11c7a133c8b33dc0c0bcf74ec (patch) | |
| tree | e22e039d9de875b0bfbee58f43d6820beddf9793 | |
| parent | 24cb586cafd40f8fbea68641f97e3431ea76c1b8 (diff) | |
| download | gcc-a28046e215307cf11c7a133c8b33dc0c0bcf74ec.zip gcc-a28046e215307cf11c7a133c8b33dc0c0bcf74ec.tar.gz gcc-a28046e215307cf11c7a133c8b33dc0c0bcf74ec.tar.bz2 | |
doc: Remove dubious example around bug reporting
gcc:
* doc/bugreport.texi (Bug Criteria): Remove dubious example.
| -rw-r--r-- | gcc/doc/bugreport.texi | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/gcc/doc/bugreport.texi b/gcc/doc/bugreport.texi index b7cfb5d..7a60324 100644 --- a/gcc/doc/bugreport.texi +++ b/gcc/doc/bugreport.texi @@ -50,11 +50,6 @@ However, you must double-check to make sure, because you may have a program whose behavior is undefined, which happened by chance to give the desired results with another C or C++ compiler. -For example, in many nonoptimizing compilers, you can write @samp{x;} -at the end of a function instead of @samp{return x;}, with the same -results. But the value of the function is undefined if @code{return} -is omitted; it is not a bug when GCC produces different results. - Problems often result from expressions with two increment operators, as in @code{f (*p++, *p++)}. Your previous compiler might have interpreted that expression the way you intended; GCC might |