[src/trunk]: src/gnu/dist/toolchain/gcc/config/i386 Back out rev. 1.4. The p...

[thorpej <thorpej%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/d386700ec4b5
branches:  trunk
changeset: 544251:d386700ec4b5
user:      thorpej <thorpej%NetBSD.org@localhost>
date:      Sat Mar 15 17:40:33 2003 +0000

description:
Back out rev. 1.4.  The problem only occurs when using pre-compiled
headers, which we turn off.  (Nevermind the mis-placed #endif which
would cause incorrect output from a non-Apple host, sigh.)

diffstat:

 gnu/dist/toolchain/gcc/config/i386/i386.c |  10 ----------
 1 files changed, 0 insertions(+), 10 deletions(-)

diffs (21 lines):

diff -r 2432968c4058 -r d386700ec4b5 gnu/dist/toolchain/gcc/config/i386/i386.c
--- a/gnu/dist/toolchain/gcc/config/i386/i386.c Sat Mar 15 16:09:34 2003 +0000
+++ b/gnu/dist/toolchain/gcc/config/i386/i386.c Sat Mar 15 17:40:33 2003 +0000
@@ -3355,17 +3355,7 @@
          if (GET_CODE (x) == CONST_INT || ! SHIFT_DOUBLE_OMITS_COUNT)
            {
              PRINT_OPERAND (file, x, 0);
-#ifndef __APPLE__
              fputs (AS2C (,) + 1, file);
-#else
-             /* The above statement results in a " ," being spit out
-                for both ANSI and traditional preprocessors.  However,
-                Apple's GCC 3.1 (which has a custom preprocessor that
-                support pre-compiled headers) that ships with OS X does
-                not like the above construct, so we hand-craft it.
-                --thorpej%netbsd.org@localhost  */
-#endif
-             fputs (" ," + 1, file);
            }
 
          return;