make allXXX - It is necessary to avoid collisions with C keywords when generating names for variables, for example: if do asm int for EOF.
+The current status of this entry is:
+++STATUS: INABIAF - please DO NOT fix
+
For more detailed information see 2024/kurdyukov4 in bugs.html.
./prog < data > out.c
- Nu HTML check this web page
+ Nu HTML check this web page
Jump to top Jump to Content Jump to Inventory
Jump to: top
-In fixing this bug you will come to a better appreciation of how the -code was able to process random data files as large as 64K.
-If you provide a random data set of about 100K bytes, the resulting C program, after taking some time, will compile:
- dd if=/dev/urandom bs=100K count=1 | ./prog > out.cHowever if increase the size of the random data set to 128K bytes, the resulting out.c C program:
dd if=/dev/urandom bs=128K count=1 | ./prog > out.c
- cc out.c -o outwill fail to compile with errors such as:
- out.c:2:...: error: expected identifier or '('
- out.c:2:...: error: expected ';' at end of declaration
- out.c:2:...: error: use of undeclared identifier 'Z'Can you fix prog.c to successfully process very large random data sets: perhaps into the gigabyte size range or larger?
How long does it take to compile the resulting out.c source?
Even better, can you fix prog.c while maintaining its style and source code layout, all without
-making the source code significantly larger?
The 2024/kurdyukov4/try.sh script +will very likely run into problems such as compile taking a long time, +compilers crashing and/or executables crashing when used with random +input sizes larger than 64K bytes.
+PLEASE NOTE: The above problems are NOT code bugs. They represent compiler mis-features, +linker limitations, and/or architecture limitations.
Jump to: top
For more information see the “Large input size issues” section of +2024/kurdyukov4/index.html.
Jump to: top