From 554fd8c5195424bdbcabf5de30fdc183aba391bd Mon Sep 17 00:00:00 2001 From: upstream source tree Date: Sun, 15 Mar 2015 20:14:05 -0400 Subject: obtained gcc-4.6.4.tar.bz2 from upstream website; verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository. --- gcc/testsuite/gcc.dg/cpp/avoidpaste2.c | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 gcc/testsuite/gcc.dg/cpp/avoidpaste2.c (limited to 'gcc/testsuite/gcc.dg/cpp/avoidpaste2.c') diff --git a/gcc/testsuite/gcc.dg/cpp/avoidpaste2.c b/gcc/testsuite/gcc.dg/cpp/avoidpaste2.c new file mode 100644 index 000000000..dc5bbc7f2 --- /dev/null +++ b/gcc/testsuite/gcc.dg/cpp/avoidpaste2.c @@ -0,0 +1,31 @@ +/* Copyright (C) 2001, 2003 Free Software Foundation, Inc. */ + +/* { dg-do preprocess } */ +/* { dg-options "-ansi" } */ + +/* This tests that we avoid accidental pasting, as well as gratuitous + space insertion, in various nasty places _inside_ a macro's + replacement list: on either side of a paste, and on either side of + an argument. It also tests that we don't pass empty macro leading + whitespace to the next line - this problem use to break Emacs + preprocessor abuse. + + Neil Booth, 1 Feb 2001. */ + +#define EMPTY_WITH_LEADING_SPACE +#define f(x, y) :x: -y##> -##y> +#define g(x, y) :x: :y##2 2##y: + +/* This should preprocess as + +: : : - > - > +:2: :22 22: + +We used to get a space at the start of the line. */ + + EMPTY_WITH_LEADING_SPACE +f(:,) +g(2, 2) + +/* { dg-final { scan-file avoidpaste2.i "(^|\\n): : : - > - >" } } + { dg-final { scan-file avoidpaste2.i "(^|\\n):2: :22 22:" } } */ -- cgit v1.2.3