From 91e3957fb0e38a5d5649f82e5d9f89dd0e85666f Mon Sep 17 00:00:00 2001 From: Mike DePaulo Date: Sat, 28 Mar 2015 09:50:31 -0400 Subject: Update openssl to version openssl-1.0.1m Conflicts: openssl/Makefile openssl/Makefile.bak openssl/crypto/cryptlib.c --- openssl/bugs/dggccbug.c | 46 +++++++++++++++++++++++----------------------- 1 file changed, 23 insertions(+), 23 deletions(-) (limited to 'openssl/bugs/dggccbug.c') diff --git a/openssl/bugs/dggccbug.c b/openssl/bugs/dggccbug.c index 30e07a60e..56f522288 100644 --- a/openssl/bugs/dggccbug.c +++ b/openssl/bugs/dggccbug.c @@ -4,17 +4,18 @@ #include -/* There is a bug in - * gcc version 2.5.8 (88open OCS/BCS, DG-2.5.8.3, Oct 14 1994) - * as shipped with DGUX 5.4R3.10 that can be bypassed by defining - * DG_GCC_BUG in my code. - * The bug manifests itself by the vaule of a pointer that is - * used only by reference, not having it's value change when it is used - * to check for exiting the loop. Probably caused by there being 2 - * copies of the valiable, one in a register and one being an address - * that is passed. */ +/* + * There is a bug in gcc version 2.5.8 (88open OCS/BCS, DG-2.5.8.3, Oct 14 + * 1994) as shipped with DGUX 5.4R3.10 that can be bypassed by defining + * DG_GCC_BUG in my code. The bug manifests itself by the vaule of a pointer + * that is used only by reference, not having it's value change when it is + * used to check for exiting the loop. Probably caused by there being 2 + * copies of the valiable, one in a register and one being an address that is + * passed. + */ -/* compare the out put from +/*- + * compare the out put from * gcc dggccbug.c; ./a.out * and * gcc -O dggccbug.c; ./a.out @@ -23,23 +24,22 @@ void inc(a) int *a; - { - (*a)++; - } +{ + (*a)++; +} main() - { - int p=0; +{ + int p = 0; #ifdef FIXBUG - int dummy; + int dummy; #endif - while (p<3) - { - fprintf(stderr,"%08X\n",p); - inc(&p); + while (p < 3) { + fprintf(stderr, "%08X\n", p); + inc(&p); #ifdef FIXBUG - dummy+=p; + dummy += p; #endif - } - } + } +} -- cgit v1.2.3