Nasal demons in preprocessor use ( [PATCH] test-suite: new preprocessor test case)

Nasal demons in preprocessor use ( [PATCH] test-suite: new preprocessor test case)

Post by Vegard Nos » Sat, 21 Mar 2009 05:30:17


2009/3/19 Ingo Molnar < XXXX@XXXXX.COM >:



Hm.

Is this really not valid C?

It worked with GCC, so I assumed it was. My mistake.

Okay, that puts us in a bit of a tight spot, with regards to kmemcheck, I mean.

Maybe I should just take up GCC development instead, and implement a
-fkmemcheck or something.

(To get rid of the bitfield false positives, I mean.)

I guess this means that kmemcheck branch should be withdrawn from
linux-next, at least temporarily, as I have no immediate
workarounds/alternatives. Stephen, can you drop it?


Vegard

--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

1. STAF(Software Testing Automation Framework) with STAX for running python test suites/cases

2. preprocessor, token concatenation, no valid preprocessor token

Hi

the following code the g++ (g++ (GCC) 3.3.3 (Debian 20040422)) emits the
error message that pasting of :: and hello is no valid preprocessor token.
The g++ 2.95.3 accepts the code. I know that handling of the ##
preprocessing operator has changed.

How I have to change the macro definiton of A(P)?
NO changes at macro calling should be necessary!

Thanks in advance!



#define A(P)int##hello(void)return?;}

class B {
public:
B()
b??;
}

private:
int;
intello();
};

A(D40);
A(B::);

int main(void){
}

3. Testing a flatfile mapping in a preprocessor

4. test test test test test test

5. Test of a preprocessor symbol defined as nothing vs. zero

6. Using Test::Unit and running operations before and after a test suite

7. In my case, is using Java preprocessor bad?

8. Testing SAP applications; writing Test Cases, Test Scripts

9. Web Testing, Example Test cases URL testing

10. Change case of string using PreProcessor

11. Can a test case tell if VERBOSE is used in pyunit test?

12. Can you help me test my MS SQL test on my new testing website

13. test suite generation for Fortran compiler testing

14. Test::Unit running all tests with automated suite

15. test-all test suite fails upon Ruby 1.8.5 compilation