procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc: Remove dubious example around bug reporting

Browse source 
gcc:
	* doc/bugreport.texi (Bug Criteria): Remove dubious example.
This commit is contained in:
Gerald Pfeifer 2024-07-07 22:01:40 +02:00
parent 24cb586caf
commit a28046e215
1 changed files with 0 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/doc/bugreport.texi
View file

@ -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